[SERVER-17504] Incorrect error on db.shutDownServer() of 1 member replica set Created: 06/Mar/15 Updated: 25/Jan/17 Resolved: 12/Mar/15 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | 3.0.0 |
| Fix Version/s: | 3.1.0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | James Wahlin | Assignee: | Benety Goh |
| Resolution: | Done | Votes: | 0 |
| Labels: | Fit&Finish | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Operating System: | ALL |
| Participants: |
| Description |
|
Running db.shutdownServer() against a one member replica set fails with an error of "No electable secondaries caught up as of" with a timestamp. This makes no sense for a one member replica set. We should either
|
| Comments |
| Comment by Githook User [ 12/Mar/15 ] |
|
Author: {u'username': u'benety', u'name': u'Benety Goh', u'email': u'benety@mongodb.com'}Message: |
| Comment by Githook User [ 11/Mar/15 ] |
|
Author: {u'username': u'benety', u'name': u'Benety Goh', u'email': u'benety@mongodb.com'}Message: Branch: master |
| Comment by Eric Milkie [ 06/Mar/15 ] |
|
We decided to amend the error message to remind users of the force option. |