Ezeelogin GUI loading slow
How to fix the slowness in loading Ezeelogin GUI
Overview: This article addresses Ezeelogin GUI slowness by disconnecting the slave node via the GUI or backend commands. Reconnect through the GUI. Avoid removing the slave node to prevent reinstallation and log loss. Disabling the slave stops data synchronization.
The slowness of GUI loading may be due to one node being unable to communicate with the other. The slowness can be fixed by disconnecting the slave node.
- It is recommended not to remove the slave node. The slave needs to be re-installed if it's removed from the master. There might be chances for losing logs if the slave got removed from the master.
- If both nodes are located in different locations, there is a chance that the distance may contribute to slowness. We would recommend you to keep the network delay between the two nodes under 15ms for faster responses.
1. How to disconnect the cluster from Ezeelogin GUI?
Step 1(A): Login to Ezeelogin GUI and click on the cluster tab. Refer below screenshot to disconnect the slave from Ezeelogin GUI.
2. How to reconnect the node from Ezeelogin GUI?
Step 2(A): Login to Ezeelogin GUI and click on the cluster tab. Refer below screenshot to connect the slave from Ezeelogin GUI.
Emergency CLI Method:
1. 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@gateway:~# php /usr/local/ezlogin/ez_queryrunner.php "update prefix_settings set value='N' where name='connected'"
2. 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'"
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:
Switching node states in Ezeelogin Cluster
Install Master/Slave Ezeelogin
Install Master/Slave Ezeelogin with MySQL SSL
How to reset cluster keys in Ezeelogin Master-slave Configuration?