[SERVER-55973] resharding_disallow_drop.js is not waiting for resharding to acquire distLocks before attempting to drop the collection Created: 09/Apr/21  Updated: 29/Oct/23  Resolved: 12/Apr/21

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

Type: Bug Priority: Major - P3
Reporter: Jordi Serra Torrens Assignee: Jordi Serra Torrens
Resolution: Fixed 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
Participants:
Linked BF Score: 70

 Description   

The resharding_disallow_drop.js test intends to wait for resharding to first acquire the db and collection distLocks here, and then attempt to drop the collection, which should fail with MaxTimeMSExpired because the distLocks are held by the resharding operation.

However, the awaitReshardingStarted function does not guarantee that the resharding operation has acquired the distLocks. It only guarantees that the resharding command started.



 Comments   
Comment by Githook User [ 12/Apr/21 ]

Author:

{'name': 'Jordi Serra Torrens', 'email': 'jordi.serra-torrens@mongodb.com', 'username': 'jordist'}

Message: SERVER-55973: resharding_disallow_drop.js is not waiting for resharding to acquire distLocks before attempting to drop the collection
Branch: master
https://github.com/mongodb/mongo/commit/48253bc972fa18dcd82ad928d8408fccf54dac89

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