[SERVER-58749] Drop database coordinator must acquire collection distributed lock Created: 22/Jul/21  Updated: 29/Oct/23  Resolved: 23/Jul/21

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

Type: Bug Priority: Major - P3
Reporter: Pierlauro Sciarelli Assignee: Pierlauro Sciarelli
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Depends
Backwards Compatibility: Fully Compatible
Operating System: ALL
Backport Requested:
v5.0
Sprint: Sharding EMEA 2021-07-26
Participants:
Linked BF Score: 148

 Description   

Acquiring the collection distributed lock for each collection getting dropped by the DropDatabaseCoordinator ensures synchronization with move chunk operations: wait to finish an eventual ongoing one and avoid starting new ones.



 Comments   
Comment by Vivian Ge (Inactive) [ 06/Oct/21 ]

Updating the fixversion since branching activities occurred yesterday. This ticket will be in rc0 when it’s been triggered. For more active release information, please keep an eye on #server-release. Thank you!

Comment by Githook User [ 27/Jul/21 ]

Author:

{'name': 'Pierlauro Sciarelli', 'email': 'pierlauro.sciarelli@mongodb.com', 'username': 'pierlauro'}

Message: SERVER-58749 Drop database coordinator must acquire collection distributed lock
Branch: v5.0
https://github.com/mongodb/mongo/commit/893f1ca7feaf279f32bf7badbdf52170a88ce803

Comment by Githook User [ 23/Jul/21 ]

Author:

{'name': 'Pierlauro Sciarelli', 'email': 'pierlauro.sciarelli@mongodb.com', 'username': 'pierlauro'}

Message: SERVER-58749 Drop database coordinator must acquire collection distributed lock
Branch: master
https://github.com/mongodb/mongo/commit/229ddfbd1e5d235e726f2e47d923231e6a9187f7

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