[SERVER-19933] check validity of "configsvr:true" at config validation time Created: 13/Aug/15 Updated: 19/Sep/15 Resolved: 17/Aug/15 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | None |
| Fix Version/s: | 3.1.7 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Eric Milkie | Assignee: | Matt Dannenberg |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Operating System: | ALL | ||||||||
| Participants: | |||||||||
| Description |
|
Currently, no check is made at config validation time if the value of "configsvr" in the new replica set config matches the value of the equivalent command line argument "--configsvr". This means if you start nodes without --configsvr and reconfig or initiate with a config that contains "configsvr:true", the reconfig or initiate command succeeds, but all nodes in the replica set immediately transition to REMOVED state. |
| Comments |
| Comment by Githook User [ 17/Aug/15 ] |
|
Author: {u'username': u'dannenberg', u'name': u'matt dannenberg', u'email': u'matt.dannenberg@10gen.com'}Message: |