[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:
Depends
is depended on by SERVER-5258 RS manager can demote current primary... Closed
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:

  1. Allow STARTUP members to sync or
  2. Have initial sync to finish by transitioning the member to recovering

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 SERVER-6214
Branch: master
https://github.com/mongodb/mongo/commit/d763ef1c9a676c43134b44fdcccddd76a55626d0

Generated at Thu Feb 08 03:11:04 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.