Graceful Shutdown
Graceful Shutdown works by transferring all the sessions stored on the server being removed from the cluster to one of the other servers in the cluster. After transferring all the sessions, the server will notify other cluster members that it has been replaced. Requests for sessions originally stored on the now terminated server will be routed to the replacement server.
It is highly recommended to perform graceful shutdowns when using Session Clustering, especially when shutting down more than one server, to avoid potential session data loss.
Important:
When a server is in the process of shutting down or is being started up after a graceful shutdown, it will not allow the session handler to create new sessions until this process is complete. You should always disconnect the server from the load balancing pool before removing it from the cluster, and only add it back to the pool after you have successfully added it to the cluster.
|
|
|
To initiate a Graceful Shutdown:
|
Note: The load will increase on active nodes during this process since some of the node's sessions are moved to other nodes. |