[SERVER-49152] Make concurrency suites always waitForDelete in v4.4 branch Created: 26/Jun/20  Updated: 06/Dec/22  Resolved: 09/Jul/20

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

Type: Bug Priority: Major - P3
Reporter: Randolph Tan Assignee: [DO NOT USE] Backlog - Sharding Team
Resolution: Duplicate Votes: 0
Labels: sharding-wfbf-day
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Related
is related to SERVER-47900 Disable checkOrphansDeleted helper in... Closed
Assigned Teams:
Sharding
Operating System: ALL
Participants:
Linked BF Score: 20

 Description   

Currently, it has a 50/50 chance of being set to true. This is problematic when the implicit multiversion suite is run as it can cause orphans to linger at the end of the test and make the orphan check hook fail.



 Comments   
Comment by Ratika Gandhi [ 09/Jul/20 ]

SERVER-47900 should do the trick. Closing this ticket in favor of SERVER-47900.

Comment by Max Hirschhorn [ 26/Jun/20 ]

The --mixedBinVersions resmoke.py command line option used by the implicit multiversion test suites would have set TestData.mixedBinVersions in the mongo shell. A test (or in this case the run_check_orphans_are_deleted.js hook) could use that to know if it is running against a mixed version cluster without interrogating the cluster.

Comment by Randolph Tan [ 26/Jun/20 ]

max.hirschhorn Either works. I think today these concurrency tests have no idea that they are running with multiversion.

Comment by Max Hirschhorn [ 26/Jun/20 ]

renctan, if we did SERVER-47900 then would we still need to do this ticket?

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