[SERVER-6214] Race condition where member gets stuck in startup and doesn't sync Created: 26/Jun/12 Updated: 11/Jul/16 Resolved: 03/Jul/12 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | 2.2.0-rc0 |
| Fix Version/s: | 2.2.0-rc0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Kristina Chodorow (Inactive) | Assignee: | Kristina Chodorow (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Operating System: | ALL | ||||||||
| Participants: | |||||||||
| Description |
|
Members don't start syncing until they're in RECOVERING state. At the end of initial sync, the member is left in STARTUP state until (fairly random) calls to rs.relinquish() move it to RECOVERING. It would be better to either:
I don't really have a preference, but I think whichever way this goes it should be in 2.2.0. |
| Comments |
| Comment by Eric Milkie [ 03/Jul/12 ] |
|
Removing from backport consideration |
| Comment by auto [ 03/Jul/12 ] |
|
Author: {u'date': u'2012-06-28T08:20:17-07:00', u'email': u'kristina@10gen.com', u'name': u'Kristina'}Message: Transition to recovering state at the end of initial sync |