[SERVER-15833] Require basic compatibility between old and new configs for force reconfig Created: 28/Oct/14 Updated: 11/Jul/16 Resolved: 28/Oct/14 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | None |
| Fix Version/s: | 2.8.0-rc0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Andy Schwerin | Assignee: | Andy Schwerin |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Minor Change |
| Operating System: | ALL |
| Participants: |
| Description |
|
Force reconfig exists to allow users to change topology when the primary is not available. It is not intended to allow users to make the cluster inconsistent by marking non-index building nodes as index-building, or arbiters as non-arbiters, e.g. |
| Comments |
| Comment by Githook User [ 28/Oct/14 ] |
|
Author: {u'username': u'andy10gen', u'name': u'Andy Schwerin', u'email': u'schwerin@mongodb.com'}Message: Force reconfig is really about letting changing topology when the primary is not |