[SERVER-3314] Segmentation Fault on Re-configuring Replica Set Created: 22/Jun/11 Updated: 29/May/12 Resolved: 22/Jun/11 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | 1.8.1 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Critical - P2 |
| Reporter: | Mike K | Assignee: | Kristina Chodorow (Inactive) |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Ubuntu Natty Narwhal, on an EC2 m2.4xlarge |
||
| Attachments: |
|
||||||||
| Issue Links: |
|
||||||||
| Operating System: | ALL | ||||||||
| Participants: | |||||||||
| Description |
|
When issuing an rs.reconfig() in the primary's console where one of the hosts' IPs were changed (secondary had died and had to be stop/started, which issued a new IP), the primary segfaulted (log attached) and had to be re-started. However, it looks like the replication set info got saved properly, as when it was re-started it connected to the secondary's new IP. |