[SERVER-5746] Wrong initialization for ReplicaSetMonitor Nodes Created: 02/May/12 Updated: 11/Jul/16 Resolved: 09/May/12 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Internal Client, Sharding |
| Affects Version/s: | 2.0.3 |
| Fix Version/s: | 2.0.6, 2.1.2 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Randolph Tan | Assignee: | Randolph Tan |
| Resolution: | Done | Votes: | 1 |
| Labels: | sharding | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Operating System: | ALL | ||||||||||||
| Participants: | |||||||||||||
| Description |
|
The nodes structure is initialized incorrectly in ReplicaSetMonitor that made them initialize to ok = false instead of ok = true. And because of 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 |
| Comments |
| Comment by auto [ 11/May/12 ] |
|
Author: {u'login': u'', u'email': u'randolph@10gen.com', u'name': u'Randolph Tan'}Message: Modified the initialization of the ok member variable of ReplicaSetMonitor::Node to true if conn smart pointer is not null. Conflicts: jstests/sharding/slaveok_routing.js |
| Comment by auto [ 09/May/12 ] |
|
Author: {u'login': u'', u'name': u'Randolph Tan', u'email': u'randolph@10gen.com'}Message: Updated test for |
| Comment by auto [ 09/May/12 ] |
|
Author: {u'login': u'', u'name': u'Randolph Tan', u'email': u'randolph@10gen.com'}Message: Modified the initialization of the ok member variable of ReplicaSetMonitor::Node to true if conn smart pointer is not null. |