Failover, failback, and session state

Should a node not be able to fulfill its duties for any reason, another mode could step in and take care of the work and data. This is called failover and is exemplified in the following diagram (true or silent failover is completely transparent to the client):

Failover, failback, and session state

Failover: Should a node in a cluster leave the cluster for some reason a client call can be handled by another node in the cluster

Should the failing node come back to work again after a period of time, work and data can be transferred back again by a failback procedure. This transfer often has some restrictions, for example, it can only happen during ...

Get WildFly Performance Tuning now with the O’Reilly learning platform.

O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.