Terracotta DB 10.1 | Terracotta Server Administration Guide | Failover
 
Failover
In a high-availability stripe, the failure of a single server represents only a small disruption, but not outright failure, of the cluster and the client operations (for related information on high availability, see the section Cluster Architecture).
In the case of a failing passive server, there is no disruption at all experienced by the clients.
In the case of a failing active server, however, there is a small disruption of client progress until a new active server is elected and the client can reconnect to it. Failover is the name given to this scenario.
Server-side implications
Once all clients have reconnected (or the reconnect window closes), the server will process all re-sent messages it had seen before for which the client had not been notified of completion.
After this, message processing resumes as normal.
Client-side implications
Clients will experience a slight stall while they reconnect to the new active server. This reconnection process involves re-sending any messages the client considers to be in-flight.
After this, client operations resume as normal.

Copyright © 2010-2019 | Software AG, Darmstadt, Germany and/or Software AG USA, Inc., Reston, VA, USA, and/or its subsidiaries and/or its affiliates and/or their licensors.
Innovation Release