Group Replication: Shipped Too Early
Group Replication: Shipped Too Early
If you care about your data, then I recommend not using Group Replication in production. It looks like it may cause headaches—and it's easy to get inconsistent results.
Join the DZone community and get the full member experience.Join For Free
Learn how real real-time monitoring is critical for DevOps. Because you can't build what you can't see.
This blog post is my overview of Group Replication technology. With Oracle clearly entering the “open-source high-availability solutions” arena with the release of their brand new Group Replication solution, I believe it is time to review the quality of the first GA (production ready) release.
Having examined the technology, it is my conclusion that Oracle seems to have released the GA version of Group Replication too early. While the product is definitely “working prototype” quality, the release seems rushed and unfinished. I found a significant number of issues, and I would personally not recommend it for production use.
It is obvious that Oracle is trying hard to ship technology to compete with Percona XtraDB Cluster, which is probably why they rushed to claim Group Replication GA quality.
If you’re all set to follow along and test Group Replication yourself, simplify the initial setup by using this Docker image. We can review some of the issues you might face together.
For the record, I tested the version based on MySQL 5.7.17 release.
No Automatic Provisioning
First off, the first thing you’ll find is there is no way to automatically set up a new node.
If you need to setup new node or recover an existing node from a fatal failure, you’ll need to manually provision the slave.
Of course, you can clone a slave using Percona XtraBackup or LVM by employing some self-developed scripts. But given the high availability nature of the product, one would expect Group Replication to automatically re-provision any failed node.
Bug: Stale Reads on Nodes
Please see this bug on getting inconsistent results on different nodes.
Here's a one line summary: While any secondary nodes are “catching up” to whatever happened on a first node (it takes time to apply changes on secondary nodes), reads on a secondary node could return stale data (as shown in the bug report).
This behavior brings us back to the traditional asynchronous replication slave behavior (i.e., Group Replication’s predecessor).
It also contradicts the Group Replication documentation, which states: “There is a built-in group membership service that keeps the view of the group consistent and available for all servers at any given point in time.” (See this documentation.)
I might also mention here that Percona XtraDB Cluster prevents stale reads.
Bug: Nodes Become Unusable After a Big Transaction
With this, they also refuse to execute further transactions.
There are two related bugs:
One line summary: After running a big transaction, any secondary nodes become unusable and refuse to perform any further transactions.
Obscure Error Messages
It is not uncommon to see cryptic error messages while testing Group Replication. For example:
<mysql> commit; ERROR 3100 (HY000): Error on observer while running replication hook 'before_commit'.
This is fairly useless and provides little help until I check the MySQL error log. The log provides a little bit more information:
2017-02-09T02:05:36.996776Z 18 [ERROR] Plugin group_replication reported: '[GCS] Gcs_packet's payload is too big. Only the packets smaller than 2113929216 bytes can be compressed.'
The items highlighted above might not seem too bad at first, and you could assume that your workload won’t be affected. However, stale reads and node dysfunctions basically prevent me from running a more comprehensive evaluation.
If you care about your data, then I recommend not using Group Replication in production. Currently, it looks like it might cause plenty of headaches, and it is easy to get inconsistent results.
For the moment, Group Replication appears an advanced — but broken — traditional MySQL asynchronous replication.
I understand Oracle’s dilemma. Usually, people are hesitant to test a product that is not GA. So, in order to get feedback from users, Oracle needs to push the product to GA. Oracle must absolutely solve the issues above during future QA cycles.
Published at DZone with permission of Vadim Tkachenko, DZone MVB. See the original article here.
Opinions expressed by DZone contributors are their own.