Seamless Session Recovery

This feature enhances session resilience and management to support high availability, improve fault tolerance,  and maximize operational flexibility. The purpose of this feature is to provide a highly available system and reduce downtime. This means that when any server/pod is brought down (for reasons such as maintenance, manual restart, worker node crash and so forth), the system will still be available for the users.

In addition, users who are actively logged into the affected server will not be logged out. Instead, they can continue their session with minimal usability impact.

This feature allow users to continue to work in the application when the server/pod is brought down, with these limitations:

• The current page reloads automatically. However, if the user was in edit mode, unsaved data will be lost.

• An error message appears, indicating that session restoration has failed. The user must re-perform their last action. 

• The restored session does not retain navigation history. Therefore, using the browser`s back button will return the user to the home page,

Here are the configuration details for Seamless Session Recovery :

• Enable the feature in the adv_cache.conf file. Refer to the “Cache Configuration” section of this guide for detailed instructions. 

• Error messages displayed when a server or pod is brought down are configurable through the MESG page. These messages are determined based on the type of page being accessed.

Note: Some pages do not belong to a specific category. In such cases, the system defaults to message code Q0298.