You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When run on an internal Kubernetes cluster, the arangoDb collections have replication factor set to one even though they are spread on three nodes. In this situation, replication factor should be at least two to be able to tolerate failure of one node.
Investigate Admin CLI, find out why this happened and make sure the replication factor is set correctly next time.
This issue is only relevant with respect to Admin CLI versions prior to 1.0, as in the 1.0 there is a CLI option to set the replication factor for all or separate collections.
When run on an internal Kubernetes cluster, the arangoDb collections have replication factor set to one even though they are spread on three nodes. In this situation, replication factor should be at least two to be able to tolerate failure of one node.
Investigate Admin CLI, find out why this happened and make sure the replication factor is set correctly next time.
This is set on per collection bases
https://docs.arangodb.com/3.11/develop/http-api/collections/#create-a-collection_body_replicationFactor
The text was updated successfully, but these errors were encountered: