-
Type:
Bug
-
Resolution: Fixed
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
Labels:
-
Environment:
*Location*: https://docs.mongodb.com/manual/tutorial/remove-replica-set-member/
*User-Agent*: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_4) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/57.0.2987.133 Safari/537.36
*Referrer*: https://www.google.com/url?q=https%3A%2F%2Fdocs.mongodb.com%2Fmanual%2Ftutorial%2Fremove-replica-set-member%2F&sa=D&sntz=1&usg=AFQjCNHyKmm1OvCObfGTs7OTn1_-sTukxQ
*Screen Resolution*: 1440 x 900
*Location*: https://docs.mongodb.com/manual/tutorial/remove-replica-set-member/ *User-Agent*: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_4) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/57.0.2987.133 Safari/537.36 *Referrer*: https://www.google.com/url?q=https%3A%2F%2Fdocs.mongodb.com%2Fmanual%2Ftutorial%2Fremove-replica-set-member%2F&sa=D&sntz=1&usg=AFQjCNHyKmm1OvCObfGTs7OTn1_-sTukxQ *Screen Resolution*: 1440 x 900
The 3rd step of rs.remove() and the 6th step of rs.reconfig() stated:
MongoDB disconnects the shell briefly as the replica set elects a new primary. The shell then automatically reconnects. The shell displays a DBClientCursor::init call() failed error even though the command succeeds.
However this re-election doesn't seem to happen all the time, while the docs stated definitively that it will happen.
It seems that this is the old behaviour that was changed in SERVER-15160.
It may be better to change the wording in the docs to be less definitive about re-election.
- is related to
-
-
- Closed
-