Details
-
Bug
-
Resolution: Fixed
-
Major
-
3.0.x, 4.0
-
*Location*: http://docs.couchbase.com/4.0/admin/Tasks/tasks-nodeFailover.html
*User-Agent*: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_10_3) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/43.0.2357.81 Safari/537.36
*Referrer*: http://docs.couchbase.com/4.0/admin/Concepts/concept-nodeFailover.html
*Screen Resolution*: 1280 x 800
*Location*: http://docs.couchbase.com/4.0/admin/Tasks/tasks-nodeFailover.html *User-Agent*: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_10_3) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/43.0.2357.81 Safari/537.36 *Referrer*: http://docs.couchbase.com/4.0/admin/Concepts/concept-nodeFailover.html *Screen Resolution*: 1280 x 800
Description
Automated failoverIt will automatically mark a node as failed over if the node has been identified as unresponsive or unavailable. There are some deliberate limitations to the auto-failover feature.
Initiating a failoverWhether you use automatic or manual failover, you need to perform additional steps to bring a cluster into a fully functioning state.
Adding nodes after the failoverAfter you resolve the issue with the failed-over node, you can add the node back to the cluster.
In this text, it appears the following three fragments are supposed to be introductory callouts, but they're up against the sentences that follow them with no space between:
- Automated failover
- Initiating a failover
- Adding nodes after the failover