How to build a multi-region, multi-master MySQL cloud database back- end capable of serving a global, high-volume cloud contact center: this global SaaS provider is a Cloud Contact Center solution provider, who needs to deliver up-to-date data to clients as quickly as possible.
Tags: AWS Cloud Disaster Recovery Multi Master MySQL use case
Oups, my previous post had a forbidden word and did not show-up on Planet MySQL, so retry...
As written in a previous post, the state of Planet MySQL is unhealthy ! I am still aggregated there for now as, before leaving what was the best news-feed for the MySQL Community, we need a replacement. This post aims at starting a discussion on this replacement.
Update
A couple of weeks ago, one of our customers reached us asking about the WARNING messages in their MySQL error log. After a while, there were a few more requests from some other customers asking whether to worry about these messages or not. In this post, I am going to write about the condition at which this WARNING message is written into the log and will explain some of the fundamentals behind the scene.
Look at the warningmber message which appears in the MySQL error log. It says it’s difficult to find a free block in the buffer pool and searched through the pool in a loop for 336 times. This is something weird to imagine; why would it have to go in a loop so many times? Let’s try to understand this.
[Warning] InnoDB: Difficult to find free blocks in the buffer pool (336 search iterations)! 0 failed attempts to flush a page! Consider increasing the buffer pool size. It is also possible that in your Unix version …
[Read more]Also, the state of bugs.mysql.com: unhealthy (last paragraph below, but this would be too long a title).
I have been complaining for some time about Planet MySQL filtering content that I think it should not. Shlomi made a courageous decision on this and explained it in his recent post (Pulling his blog out of Planet MySQL aggregator, over community concerns). I am thinking of doing
Usually one would expect that ALTER TABLE with ALGORITHM=COPY will be slower than the default ALGORITHM=INPLACE. In this blog post we describe the case when this is not so.
One of the reasons for such behavior is the lesser known limitation of ALTER TABLE (with default ALGORITHM=INPLACE) that avoids REDO operations. As a result, all dirty pages of the altered table/tablespace have to be flushed before the ALTER TABLE completion.
Some history
A long time ago, all “ALTER TABLE” (DDLs) operations in MySQL were implemented by creating a new table with the new structure, then copying the content of the original table to the new table, and finally renaming the table. During this operation the table was locked to prevent data inconsistency.
Then, for InnoDB tables, the new algorithms were introduced, which do not involve the full table copy and some operations do not apply the table level lock – first the online …
[Read more]So, I admit the title for this post is a bit ambiguous. Not only is it the second post I’ve written in a short period of time, but it’s also focused on ProxySQL 2.0. As promised in the previous post, I’ve upgraded my testing environment to ProxySQL 2.0 and was interested to see if there are any differences in behaviour from the previous version. As it turns out, there are.
In the comments section of the previous post, you’ll find a comment by ProxySQL Founder and CEO, René Cannaò:
“Indeed ProxySQL doesn’t support caching_sha2_password authentication plugin, but since ProxySQL 2.0.3 (March 2019) a client connection using caching_sha2_password will be automatically switched to mysql_native_password.
With regards to “OPT_CHARSET_NAME=utf8”, the problem is that your backend it is not MySQL 8.0 …
[Read more]
I have added two more videos to my MySQL
Document Store Tutorials for your viewing pleasure. Early in
May I will be presenting a webinar that will be an introduction
to the Document Store which will cover much of this
material. If there is any specific that you want covered
please let me know.
The first video is on how to use the Document Store to access
relational tables. Yes, from the NoSQL side of the server
you can reach the structured data.
And the second video explains the _id field which is needed as a
primary key for the storage engine, how you can supply you own
values (no conflicts please), and how the server will generate
values.All opinions expressed in this blog are those of Dave
Stokes who is actually amazed to find anyone else agreeing with
him
This presentation covers about the basics of Group replication in MySQL 8.0. Group replication world on the basis of Multi Paxos ( a variant of it ). The author covers the leader election algorithm , switching the primary node and replication modes in this presentation.
Group Replication in MySQL 8.0 ( A Walk Through ) from Mydbops
Like to have this high availability MySQL solution configured on your environment. Mydbops Consultants can provide the best solution with right cost for performance.
Let’s continue our series of using OCI to install popular Open Source programs with MySQL 8.0. After WordPress, Drupal, it’s not the Moodle’s turn!
This is a request from my Japanese colleague Machiko
We will use two different compute instances:
The application server will be reachable from the Internet on port 22 (ssh) and 80 (http). The database server won’t be reachable from outside, we will have to use the application server as jumphost to install the server.
This is an overview of the proposed architecture:
Deploying 2 compute instances
The first step is to install 2 compute instances, one in the Public Subnet and one in the Private Subnet.
We first start with the application server (called myMoodle):
As the second instance will be located …
[Read more]How to serve global IoT customers in the cloud – and secure SaaS revenue using Tungsten Clustering on cloud-based database services
SaaS providers typically rely on providing a quality service across multiple locations, with the best application and database availability. They tend to be growth-oriented and need to ensure that their business will always be available without having to worry about how their databases will achieve continuous operations.
Our customer for this use case is a global SaaS provider with an open data exchange platform for the Internet of Things (IoT) that has customers all over the globe.
This use case looks at how our customer migrated from a single region Amazon RDS deployment to a truly global, geo-distributed multi-master Tungsten Clustering database solution – a better, more scalable solution at a lower total cost. And how they did so without having to change their application, all the …
[Read more]