-
Type: Bug
-
Resolution: Done
-
Priority: Major - P3
-
Affects Version/s: 2.0.3
-
Component/s: Internal Client, Sharding
-
ALL
The nodes structure is initialized incorrectly in ReplicaSetMonitor that made them initialize to ok = false instead of ok = true. And because of SERVER-5405, the node can forever be marked as not ok. The side effect is that every time a connection needs to get the master, it will call isMaster & replsetGetStatus (in the normal case, will never get called because node is ok).
This also means that slaveOk will never work on a sharded environment with auth because the secondaries will be marked as bad nodes from the start and will never be able to recover from it (Without SERVER-5405's fix).
- is related to
-
SERVER-5405 mongos does not send reads to secondaries after replica restart when using keyFiles
- Closed