The master-slave setup is for High Availability (HA). Data between the master and slave is replicated in real-time. If the primary node goes down, the Ezeelogin admin user can switch the secondary node to the master state and all users can continue to work from the secondary node. The node with the master state will handle read and write operations, while the node with the slave state will only handle read operations. When the primary node becomes accessible, Ezeelogin will automatically switch back to the master state in the primary node and data will be replicated from the secondary node. Admin users can switch the state from slave to master at any time in the Ezeelogin GUI. The master state will always allow read and write operations, while the slave state will only allow read operations. The state will be changed according to the admin user's preference, but node states will remain unchanged throughout their lifetime.