[SERVER-58273] Solve deadlock caused by uninterruptible lock guard in drop db participant command Created: 06/Jul/21  Updated: 29/Oct/23  Resolved: 07/Jul/21

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

Type: Bug Priority: Major - P3
Reporter: Pierlauro Sciarelli Assignee: Tommaso Tocci
Resolution: Fixed Votes: 0
Labels: PM-1965-Cleanup
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Backwards Compatibility: Fully Compatible
Operating System: ALL
Backport Requested:
v5.0
Sprint: Sharding EMEA 2021-07-12
Participants:

 Description   

The UninterruptibleLockGuard in the drop database participant command can end up causing a deadlock in the same way it was happening for the drop collection participant command (complete explanation in this comment from SERVER-57756 ).

Probably it's possible to adopt a solution similar to the one committed for SERVER-58143 .



 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 [ 20/Jul/21 ]

Author:

{'name': 'Tommaso Tocci', 'email': 'tommaso.tocci@mongodb.com', 'username': 'toto-dev'}

Message: SERVER-58273 Solve deadlock caused by uninterruptible lock guard in drop db participant command

(cherry picked from commit 2a41fb45f89a9b7b51053f9b448d767ba074684e)
Branch: v5.0
https://github.com/mongodb/mongo/commit/5e048e396e59172c86f8621a4ad4bf009012d130

Comment by Githook User [ 07/Jul/21 ]

Author:

{'name': 'Tommaso Tocci', 'email': 'tommaso.tocci@mongodb.com', 'username': 'toto-dev'}

Message: SERVER-58273 Solve deadlock caused by uninterruptible lock guard in drop db participant command
Branch: master
https://github.com/mongodb/mongo/commit/2a41fb45f89a9b7b51053f9b448d767ba074684e

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