Spotfire Server uses session clustering as a failover mechanism to manage user sessions in an event when nodes in Spotfire Server cluster become unavailable.
Session clustering
Session clustering enables users to continue their work without interruption even if a server goes down or must be restarted.
The sessions are stored in a shared in-memory store, so there must be at least one additional server online (within the same site) for the session to be kept. Note that there is no persistent storage available, so if all servers in a site are restarted at the same time, then the sessions will be lost.
The end-user will normally not notice that a session is handed over to another server, with the following exceptions:
- If the user had an ongoing execution of an information link on the server that went down.
- If the user was saving to or opening anything from the library on the server that went down.
- If an administrator user was deploying packages (using the Deployment & Packages app).
To disable the session clustering, change the
clustering.session-clustering.enabled configuration property to false (the default is true), using the set-config-prop command:
config export-config --force
config set-config-prop -n clustering.session-clustering.enabled -v false
config import-config -c "Disabled session clustering"For more information, see Spotfire Server Administration Guide:
https://docs.tibco.com/pub/spotfire_server/14.0.6/doc/html/TIB_sfire_server_tsas_admin_help/server/topics/clustered_server_deployments.html