[SERVER-13500] Changing replica set configuration can crash running members Created: 06/Apr/14 Updated: 11/Jul/16 Resolved: 10/Apr/14 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | 2.6.0-rc3 |
| Fix Version/s: | 2.6.1, 2.7.0 |
| Type: | Bug | Priority: | Critical - P2 |
| Reporter: | Akshay Kumar | Assignee: | Eric Milkie |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Operating System: | Linux | ||||||||
| Backport Completed: | |||||||||
| Participants: | |||||||||
| Description |
|
Issue Status as of April 15, 2014 ISSUE SUMMARY USER IMPACT WORKAROUNDS RESOLUTION AFFECTED VERSIONS PATCHES Original descriptionIf in the process of removing a member from a replica set, the member is removed from the configuration while still running, a mongod may crash. To avoid this bug, please follow the documented procedure below for removing a node and shut down the member before removing it from the configuration: Example of what a crash may look like:
|
| Comments |
| Comment by Githook User [ 10/Apr/14 ] |
|
Author: {u'username': u'dannenberg', u'name': u'matt dannenberg', u'email': u'matt.dannenberg@10gen.com'}Message: (cherry picked from commit ba3823f2a7c08a022bebbe8accebba8893582e09) |
| Comment by Githook User [ 09/Apr/14 ] |
|
Author: {u'username': u'dannenberg', u'name': u'matt dannenberg', u'email': u'matt.dannenberg@10gen.com'}Message: |