[SERVER-9719] sharding_multiple_ns_rs.js use wait logic instead of sleep to make sure new primary is online Created: 17/May/13  Updated: 11/Jul/16  Resolved: 17/May/13

Status: Closed
Project: Core Server
Component/s: Testing Infrastructure
Affects Version/s: None
Fix Version/s: 2.4.4, 2.5.0

Type: Bug Priority: Major - P3
Reporter: Greg Studer Assignee: Greg Studer
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Operating System: ALL
Participants:

 Description   

We currently sleep() to ensure that a new primary comes online after an old primary goes down, this causes intermittent failures in the test.

http://buildlogs.mongodb.org/Nightly%20Windows%2064-bit/builds/1276/test/slow%20nightly/sharding_multiple_ns_rs.js



 Comments   
Comment by auto [ 22/May/13 ]

Author:

{u'username': u'gregstuder', u'name': u'Greg Studer', u'email': u'greg@10gen.com'}

Message: SERVER-9719 sharding_multiple_ns_rs.js wait for mongos to detect primary failover
Branch: v2.4
https://github.com/mongodb/mongo/commit/69f84b299776ec2f8b0ae29b95e82f6baf20fa3b

Comment by auto [ 17/May/13 ]

Author:

{u'date': u'2013-05-17T14:30:22Z', u'name': u'Greg Studer', u'email': u'greg@10gen.com'}

Message: SERVER-9719 sharding_multiple_ns_rs.js wait for mongos to detect primary failover
Branch: master
https://github.com/mongodb/mongo/commit/7147f38909978e83f290a31a0b5833b097bab5db

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