Group Replication is the main component of the future MySQL HA solution. Even if with GR, it’s possible to write simultaneously on all the member of the group, GR doesn’t provide any write scaling. Indeed, if one member reached 100% of its write capabilities, adding writes to another member, won’t help as both will have to write their load AND the load from the other member: remember this is (virtual) synchronous replication, all writes happening on member A will happen on member B and on all other members of the group.
As you can read above, Group Replication has its own terminology:
- a cluster is called a GROUP
- a node is called a MEMBER
This article is the first of a new series related to Group Replication.
Don’t forget that the MySQL Team will propose several sessions on GR at Oracle Open World 2016 (OOW):
- MySQL High Availability with Group Replication [CON4669] by Nuno Carvalho
- Building a Highly Available MySQL Database Service with Group Replication [HOL2912] by Matt Lord
- MySQL Group Replication in a Nutshell: Hands-on Tutorial [TUT6394] by myself
I will also present an hands-on tutorial on Group Replication at Percona Live Amsterdam with my friend Kenny Gryp.
And finally, don’t miss the awesome articles from the development team on mysqlhihavailability’s blog.