| Jive and High-Availability / Failover Behavior of HA Servers | |
If/when a cache server becomes unavailable, the web application nodes will continue indefinitely to attempt to communicate with the cache server until it is brought back online.
A web application node will determine that a cache server is unavailable after 20 consecutive failed requests to the cache server. The web app node will then wait for two seconds before attempting to communicate again with that cache server. This process will continue indefinitely until the failed cache server is brought back online. In the meantime, the web app nodes will automatically redirect to the next available cache server(s).
If the cache server is unavailable at the startup of a web application node, the web node will use local caching. The web app node will continue to try to communicate with the external cache server, and will do so indefinitely, until the external cache server is brought back online.