This is a description of the simplest case of 2-phase commit (2PC) in NDBCluster: one transaction, containing a single insert, update or delete operation on a single row. The PREPARE phase of the 2PC is initiated by the API node (which is a mysqld or a NoSQL client) sending a TCKEYREQ to the Transaction Coordinator of a data node.…
10 Older Entries »
Percona Live Amsterdam is just finished… there was an entire room full day about MySQL 8.0 which is wonderful but there was also another product that everybody was talking about: ProxySQL (great job René).
Having used already ProxySQL for Group Replication and other tests, I knew that it would be possible to use it also for this purpose. After a very short discussion and a nightly chat with …[Read more]
We are very excited about the next release of MySQL Group Replication 0.9.0 in MySQL 5.7.15 and the great work that has been done to improve its stability. Release after release, MySQL Group Replication becomes more stable and more user-friendly and has reached a maturity level that made us declare 0.9.0 a release candidate.…
There was a bold announcement during the MySQL Keynote at Oracle Open World. A new product that will mix up with the existing GA server, called MySQL InnoDB Cluster. This is an evolution of MySQL group replication, which has been in the labs for long time, and the MySQL shell, which was introduced as a side feature last April. The boldness I mentioned before is on account of wanting to add to a GA server something that was defined as release candidate despite never having been out of the labs. The product is interesting as it promises to be a quick and painless cluster deployment, with built-in high availability and scalability.
Yesterday I was in Paris to attend a OpenTech Meetup related to MySQL.
You can find below the two presentations I gave (Warning: in French).
The audience was very interested and I got …[Read more]
After having played with MySQL Group Replication and HAProxy, it’s time to show you how easy it’s to setup MySQL HA with ProxySQL.
If you remember, I wrote in my last post that it is recommended to use Group Replication with only one WRITER group member. As it is the preferred architecture, I will show you how to achieve this using ProxySQL. With ProxySQL, you don’t need to have two different interfaces to split reads and writes.
In fact, when you use ProxySQL, you have a much larger amount of options to route your queries. In production, the smart DBA, will identify …[Read more]
MySQL Group Replication is just one component of the upcoming MySQL HA Solution as Matt Lord explained it in his GR quick start guide. So while mysql-router is back to school to become smarter and learn how to take the right decision we can already use existing 3rd party solutions. To be honest, if people are already using a load balancer/proxy with MySQL asynchronous, semi-sync or other virtual synchronous solution and want to evaluate and migrate to MySQL’s native Group Replication, they might not migrate load balancer at the same time as they move to GR. Step-by-step migration, one component at the time is always recommended in complex architecture.
So in this post, I want to cover HAProxy and a dedicated health check related to what might be the more common architecture. Matt already explained in his start guide how to use …[Read more]
Please join Percona, Technical Account Manager, Michael Patrick on Thursday, June 23, 2016 at 10 AM PDT (UTC-7) as he presents “Choosing a MySQL High Availability Solution Today.”
High availability (HA) is one of the solutions to improve performance, avoid data outages, and recover quickly from disasters. An HA environment helps guarantee that your database doesn’t have a single point of failure, accommodates rapid growth and exponentially increasing database size, and enables the applications that power your business.
Michael will discuss various topologies for achieving High Availability with MySQL.
- Percona XtraDB Cluster
- MySQL Orchestrator
Each solution has advantages and …[Read more]
What is Orchestrator?
Orchestrator is a replication topology manager for MySQL.
It has many great features:
- The topology and status of the replication tree is automatically detected and monitored
- Either a GUI, CLI or API can be used to check the status and perform operations
- Supports automatic failover of the master, and the replication tree can be fixed when servers in the tree fail – either manually or automatically
- It is not dependent on any specific version or flavor of MySQL (MySQL, Percona Server, MariaDB or even MaxScale binlog servers)
- Orchestrator supports many different types of topologies, from a single …
The MySQL Fabric team is pleased to announce that a new version
is now available on Labs. This labs release includes our latest
developments to give you a taste of what we have been working on.
In particular, it includes the following new features and
- Multi-node Fabric support is now available! This means that multiple fabric nodes can be started and any node can be contacted to perform operations. This allows Fabric itself to be fault-tolerant (no single point of failure) and distribute request across multiple Fabric nodes. For more information, see: Increasing MySQL Fabric Resilience to Failures: Meet the Multi-Node Fabric
- Improved security password management, allowing password to not be passed in plain text in the command line or configuration files. …
10 Older Entries »