ArangoDB v3.8 reached End of Life (EOL) and is no longer supported.
This documentation is outdated. Please see the most recent version at docs.arangodb.com
Active Failover Limitations
The Active Failover setup in ArangoDB has a few limitations. Some of these limitations may be removed in later versions of ArangoDB:
- Should you add more than one follower, be aware that during a failover situation the failover attempts to pick the most up to date follower as the new leader on a best-effort basis.
- In contrast to full ArangoDB Cluster (with synchronous replication), there is no guarantee on how many database operations may have been lost during a failover.
- Should you be using the ArangoDB Starter or the Kubernetes Operator to manage your Active-Failover deployment, be aware that upgrading might trigger an unintentional failover between machines.