Details
-
Improvement
-
Resolution: Done
-
Minor - P4
-
None
-
*Location*: http://docs.mongodb.org/manual/reference/method/rs.add/#rs.add
*User-Agent*: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_7_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/28.0.1500.95 Safari/537.36
*Referrer*: http://docs.mongodb.org/manual/reference/replica-commands/
*Screen Resolution*: 2560 x 1440
*repo*: docs
*source*: reference/method/rs.add
*Location*: http://docs.mongodb.org/manual/reference/method/rs.add/#rs.add *User-Agent*: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_7_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/28.0.1500.95 Safari/537.36 *Referrer*: http://docs.mongodb.org/manual/reference/replica-commands/ *Screen Resolution*: 2560 x 1440 *repo*: docs *source*: reference/method/rs.add
Description
Hi,
This pages states that: "This function will disconnect the shell briefly and forces a reconnection as the replica set renegotiates which member will be primary. As a result, the shell will display an error even if this command succeeds.".
Can you validate this statement? My understanding is that, for an additive change, there is no actual re-negotiation of which member is primary unless there are other configuration changes taking place, or if there is no chaining allowed.
https://github.com/mongodb/mongo/blob/master/src/mongo/db/repl/rs.cpp#L602-L616
Thanks.