[SERVER-26484] Black-list jumbo1.js from continuous stepdown suite on 3.2 branch Created: 05/Oct/16  Updated: 13/Jul/19  Resolved: 07/Oct/16

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

Type: Task Priority: Major - P3
Reporter: Andy Schwerin Assignee: Andy Schwerin
Resolution: Done Votes: 0
Labels: test-only
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Backwards Compatibility: Fully Compatible
Sprint: Sharding 2016-10-10, Sharding 2016-10-31
Participants:
Linked BF Score: 0

 Description   

jumbo1.js starts the balancer in the middle of execution. The 3.2 branch doesn't support automatically retrying that operation, because it's done in the shell rather than through a command running on mongos. Since the test cannot be fixed using features available in 3.2, we should blacklist the test in the continuous stepdown suite on that branch.



 Comments   
Comment by Siyuan Zhou [ 13/Jul/19 ]

The last commit b690ca960 should be part of SERVER-26494.

Comment by Githook User [ 28/Feb/17 ]

Author:

{u'username': u'benety', u'name': u'Benety Goh', u'email': u'benety@mongodb.com'}

Message: SERVER-26484 removed unreachable code in SyncSourceFeedback. Blacklisting of reporter sync source will be done in BackgroundSync and SyncSourceResolver.
Branch: master
https://github.com/mongodb/mongo/commit/b690ca960b5062ee5b8af034ffe338051a228431

Comment by Githook User [ 07/Oct/16 ]

Author:

{u'username': u'andy10gen', u'name': u'Andy Schwerin', u'email': u'schwerin@mongodb.com'}

Message: SERVER-26484 Blacklist sharding/jumbo1.js form sharding continuous csrs stepdown suite

This test starts the balancer by doing a non-retryable config server write.
Branch: v3.2
https://github.com/mongodb/mongo/commit/ae46881f1a59d341507fbc7179790896c1ccec7e

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