[SERVER-3010] replica set reconfiguration results in NULL _self in ReplSetImpl Created: 27/Apr/11 Updated: 29/May/12 Resolved: 12/Jul/11 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | 1.9.1 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Greg Studer | Assignee: | Unassigned |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Linux 64 bit Legacy, potentially others |
||
| Operating System: | Linux |
| Participants: |
| Description |
|
NULL _self value after (many) reconfigurations, when the reconfiguration data actually does contain the server host/port doing the reconfiguration. Can be tracked by a NULL _self value in ReplSetImpl::syncThread after running many tests from jstests/repl/priority1.js. Bandaged the problem so far by disabling the sync when self is not detected after the reconfigure. See https://github.com/mongodb/mongo/commit/a4467c4849e2032f682598e06ba5437e843d1125 |
| Comments |
| Comment by Kristina Chodorow (Inactive) [ 12/Jul/11 ] |
|
Same as |
| Comment by Greg Studer [ 27/Apr/11 ] |
|
also noticed that _members contains only a single Member when _self is NULL |