[SERVER-7177] state transition for replica sets isn't correct Created: 26/Sep/12  Updated: 11/Jul/16  Resolved: 10/Oct/12

Status: Closed
Project: Core Server
Component/s: Replication
Affects Version/s: 2.2.0
Fix Version/s: 2.2.1

Type: Bug Priority: Major - P3
Reporter: Eric Milkie Assignee: Kristina Chodorow (Inactive)
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to SERVER-3251 Overflowed replica set members briefl... Closed
is related to SERVER-7186 Batched oplog application increases f... Closed
Operating System: ALL
Participants:

 Description   

A node that is initial syncing is in state STARTUP2. If all goes well, it transitions to state SECONDARY, then RECOVERING, then back to SECONDARY. The first SECONDARY state is a mistake; it should go straight to RECOVERING.



 Comments   
Comment by auto [ 01/Oct/12 ]

Author:

{u'date': u'2012-09-28T08:21:43-07:00', u'email': u'kristina@10gen.com', u'name': u'Kristina'}

Message: SERVER-7177 Added test for minvalid startup
Branch: master
https://github.com/mongodb/mongo/commit/afd0caeb66ae9864e634238f1cbfe0867d876470

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