Details
-
Bug
-
Resolution: Unresolved
-
None
-
None
-
None
-
*Location*: https://docs.couchbase.com/server/current/cli/cbcli/couchbase-cli-setting-autofailover.html
*Referrer*: https://docs.couchbase.com/server/current/learn/clusters-and-availability/groups.html
*User-Agent*: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/107.0.0.0 Safari/537.36
*Screen Resolution*: 1536 x 864*Location*: https://docs.couchbase.com/server/current/cli/cbcli/couchbase-cli-setting-autofailover.html *Referrer*: https://docs.couchbase.com/server/current/learn/clusters-and-availability/groups.html *User-Agent*: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/107.0.0.0 Safari/537.36 *Screen Resolution*: 1536 x 864
Description
CB 7.1 support concurrent failover of more than 3 nodes, see
https://docs.couchbase.com/server/current/learn/clusters-and-availability/groups.html#defining-groups-and-enabling-group-failover
Rest API parameter maxCount seems to support this (the docs changed between v7.0 and v7.1): https://docs.couchbase.com/server/current/rest-api/rest-cluster-autofailover-enable.html
However, parameter --max-failovers <num> on this page does not seem to allow a value greater than 3.
Reporter: Florian Kelbert
E-mail: florian.kelbert@couchbase.com