[SERVER-2483] "need most members up to reconfigure" but most members are up Created: 05/Feb/11 Updated: 12/Jul/16 Resolved: 08/Feb/11 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | 1.7.5 |
| Fix Version/s: | 1.7.6 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | David Mytton | Assignee: | Kristina Chodorow (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Operating System: | ALL |
| Participants: |
| Description |
|
Most members are up and rs.reconfig() command sent to primary, but still seems to require all members be up. set2:PRIMARY> rs.status() , , , , , |
| Comments |
| Comment by auto [ 08/Feb/11 ] |
|
Author: {u'login': u'kchodorow', u'name': u'Kristina', u'email': u'kristina@10gen.com'}Message: skip heartbeat check on self |
| Comment by Kristina Chodorow (Inactive) [ 08/Feb/11 ] |
|
If you try it a second time, does it succeed? If not, can you send the logs from around the reconfig? |