Skip to Content

Switching node states in Ezeelogin Cluster

368  Nesvin KN May 26, 2026  Features & Functionalities

Switch the node state from slave to master in the Ezeelogin cluster

Overview: This article describes how to switch a node from Slave to Master in Ezeelogin by verifying database synchronization, promoting the Slave node to Master, and refreshing the browser to update the node state.

If the Master node state has changed to the slave state, you would like to revert it to how it was originally since the master node is back online.

1. Login into the GUI of the current slave node -> click on Cluster -> Verify database to ensure that databases are in sync before switching node roles.



2. Once the databases are in sync (identical) after verifying the database, click on "Cluster" > "Make master" on the current slave node.

 3. Refresh the browser tab to view the updated node state. Refer to the below screenshot.

Emergency CLI Method:

How to disconnect the cluster from the backend? 

If a user cannot disconnect the slave from the Ezeelogin master GUI, run the below command on the current master node to disconnect from the backend.

root@current_master_node:~# php /usr/local/ezlogin/ez_queryrunner.php "update prefix_settings set value='N' where name='connected'"

How to disconnect and switch the node state of the cluster from the backend?

If a user cannot switch node state from Ezeelogin GUI, run the below commands on the gateway server.

root@gateway:~# php /usr/local/ezlogin/ez_queryrunner.php "update prefix_settings set value='master' where name='nodestate'"

root@gateway:~# php /usr/local/ezlogin/ez_queryrunner.php "update prefix_settings set value='N' where name='connected'"

View Cluster logs / Node State  (Master/Slave) Change Logs in the GUI

   Cluster logs provide details about when the node state changes and the reason for switching between the master and slave states.

cluster log

In the above sceenshot the reason “takeover initiated by user” indicates that a user manually changed the secondary node from the slave state to the master state. A “remote to local commit” can occur during server disconnect and reconnect events, typically when the master and slave nodes resynchronize after connectivity is restored.

FAQ:

1. Can we disable the slave server since we are currently using only the master node? 

Certainly, the choice to disable the slave server is yours, but keep a note that data synchronization between the master and slave servers will not occur if the slave is disabled. It is recommended to keep both servers running and synchronized for real-time data updates, as changes made to the master server will automatically sync with the slave server.

Related Articles:

Explanation of cluster
Install Cluster/Secondary node

Verify the Database to sync tables in a database

Reset Cluster Keys
Rating: 5 (1 Votes)