[SERVER-26516] replicaset fixture await_ready should wait for initial sync node to be ready Created: 07/Oct/16  Updated: 19/Nov/16  Resolved: 14/Oct/16

Status: Closed
Project: Core Server
Component/s: Replication, Testing Infrastructure
Affects Version/s: None
Fix Version/s: 3.4.0-rc1

Type: Bug Priority: Major - P3
Reporter: Judah Schvimer Assignee: Robert Guo (Inactive)
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: TIG 2016-10-31
Participants:
Linked BF Score: 0

 Description   

Currently we reduce the number of retries for initial sync to 1 for all nodes in the replicaset during the static initial sync passthroughs. Nodes undergo initial sync during the IntermediateInitialSync hook, but also during normal fixture startup. During the hook there are no ops to apply so we expect no initial sync restarts. During normal fixture startup it is possible for there to be ops to apply because we do not wait for the initial sync node to be in SECONDARY state before beginning the tests on the primary. The dynamic initial sync passthroughs will not lose coverage as they will just restart the initial sync node after the first test.



 Comments   
Comment by Githook User [ 14/Oct/16 ]

Author:

{u'username': u'guoyr', u'name': u'Robert Guo', u'email': u'robert.guo@10gen.com'}

Message: SERVER-26516 resmoke should wait for initsync node to be in SECONDARY state before running tests
Branch: master
https://github.com/mongodb/mongo/commit/240a12e251db3fac5c2eeaaf2340e03a0d0288bb

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