MySQL Database Service & NDB Cluster

In this blog, we will discuss about bidirectional replication between two NDB clusters. With this topology, user can do transaction simultaneously from both the clusters on the same database objects. Let’s create two MySQL NDB Cluster with the following environment, Here, both will be termed as ‘source’ cluster as well as ‘replica’ cluster as we will do replication from both the sides. MySQL NDB Cluster version (Latest GA version) 1 Management node 4 Data nodes 2 MySQLDs Configuration slots for up to 4 additional API nodes Replication schema diagram:                     |----------- S1 ---------->>----------S3--------------|                          |                                              ...

In the previous blog, we were able to setup a MySQL NDB Cluster replication between one source and one replica cluster. In this blog, we will discuss about replication between one source and three replica clusters. Note: With MySQL version (8.0.21), we have started changing the term “master” to “source”, the term “slave” to “replica”. So in this blog we will refer these terms ‘source’ and ‘replica’ wherever applicable. The main advantage of this type of topology is good for giving ‘local’ reads in geographically distant areas as well as increased redundancy in case of issues. Let’s create four MySQL NDB Cluster with the following environment, from which one will be termed as ‘source’ cluster while the rest will be ‘replica’ clusters. MySQL NDB Cluster version (Latest GA version) 1 Management node 4 Data nodes 1 MySQLD Configuration slots for up to 4 additional API nodes Replication schema diagram: M y SQL ( test01 ) - ---->------->------->------> MySQL ( test05 ) ( CLUST...

In this blog series, we will discuss various MySQL NDB Cluster replication topologies possible with a demonstration. We will start with a simple case i.e. one source (formerly called master) and one replica (formerly called slave). Note: With MySQL version (8.0.21), we have started changing the term “master” to “source”, the term “slave” to “replica”. So in this blog we will refer these terms ‘source’ and ‘replica’ wherever applicable. Let’s create two MySQL NDB Cluster with the following environment, from which one will be termed as ‘source’ cluster while the other one will be ‘replica’ cluster. For now, let’s stick to the identical environment from both the cluster. Later in the following blog series, we will change the environments and will run the replication. MySQL NDB Cluster version (Latest GA version) 1 Management node 4 Data nodes 1 Mysqld Configuration slots for up to 4 additional API nodes Replication schema diagram:    CLUSTER A         ...