[SERVER-22157] Force primary config server step down in sharding_continuous_config_stepdown suite Created: 12/Jan/16  Updated: 17/Jan/17  Resolved: 08/Mar/16

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: None
Fix Version/s: 3.3.3

Type: Task Priority: Major - P3
Reporter: Dianna Hohensee (Inactive) Assignee: Dianna Hohensee (Inactive)
Resolution: Done Votes: 0
Labels: bkp
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Tested
tested by SERVER-22239 wait for replication after duplicate ... Closed
tested by SERVER-22241 "not master and slaveOk=false" error ... Closed
Backwards Compatibility: Fully Compatible
Backport Requested:
v3.2
Sprint: Sharding F (01/29/16), Sharding 10 (02/19/16), Sharding 11 (03/11/16)
Participants:

 Description   

Implement less graceful stepdown with rollbacks in sharding_continuous_config_stepdown testing suite.



 Comments   
Comment by Githook User [ 08/Mar/16 ]

Author:

{u'username': u'DiannaHohensee', u'name': u'Dianna Hohensee', u'email': u'dianna.hohensee@10gen.com'}

Message: SERVER-22157 force config primary stepdown in sharding_continuous_config_stepdown testing suite
Branch: master
https://github.com/mongodb/mongo/commit/8f1e89803e2239bd31ecb53c85245a249b7e04ce

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