Single Connect Redundancy Testing

redundancy testing health check control is done with http request to port 80 or 443 receiving http code 200 ok as a response means that the service is up the mentioned control is performed by the load balancer belonging to the company single connect nodes do not load balancing within themselves requires independent load balancer for load balancing two methods are available for single connect to control redundancy redundancy control can be done by stopping the related service of single connect it will be sufficient to run the following commands in the cli with the authorized user ui service systemctl stop netright tomcat proxy services systemctl stop nssoapp systemctl stop sftp prox after the related services are stopped, the load balancer health check will fail and all traffic should be forwarded to other nodes after the load balancer directs the traffic, it is seen that the data in the single connect is up to date and there is no problem in receiving the traffic single connect provides data redundancy with database when the services at the application level are stopped, the database will continue to be redundant ui and proxy start command systemctl start nssoapp systemctl start sftp prox systemctl start netright tomcat redundancy control can be done by shutdown the single connect server after shutting down single connect server, the load balancer health check will fail and all traffic should be forwarded to other nodes after the load balancer directs the traffic, it is seen that the data in the single connect is up to date and there is no problem in receiving the traffic when server is turned on again, the difference between the database will be synchronized by the replication during the synchronization process, the server will be actively available single connect nodes will continue to provide up to date services in structures where load balancer is not used, single connect can continue to use and redundancy test by accessing the other node ip address