Cluster of replicated nodes
Configuring the slave.
The slave node acts as the failover in case the primary goes down. Its always recommended to setup the slave node so that server are accessible at all times just in case the primary nodes is accessible due to hardware or network failures.
Before you begin the installation of the slave node..
- Make sure that the slave ip is licensed.
- Make sure that mysql server is running on the slave.
- Make sure the firewall on master does not block mysql and ssh connections initiated from the slave.
- On the slave node, download the same binary package that was used on primary. This is to ensure that the master and the slave node uses the same version of Ezeelogin for the cluster to work.
Run the command on the slave/secondary server to install Ezeelogin slave.
sh ezlogin_5.9.26.bin -- -secondary -othernode 172.16.9.247
and follow the on screen instructions.
Once the slave has been setup, the cluster tab on master would looks as follows.
- Node state Show the current state of the node.
- master Add/Edit operation can be performed only in this mode.
- slave Read only mode of operation.
- Other node Show the state of the other node in the cluster. Click to remove the slave node from cluster.
- Status Shows the connection state between the nodes. Click to break out of the cluster and run independently.
- Verfiy database This would check if the dbs are identical on the master and slave. It would show if there are any differences in the database tables and would prompt the user to resolve any inconsistencies that may arise.
- Reset this node Fingerprint Use this to reset the fingerprint of the current node if its SSH identification has changed.
Once the slave has been setup, the cluster tab on slave would looks as follows. Note the Node state Slave for the secondary node. Click to turn the slave into master node if the master fails.