[SERVER-58167] Use scoped database critical section during dropDatabase Created: 30/Jun/21  Updated: 29/Oct/23  Resolved: 05/Jul/21

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: 5.1.0, 5.0.0-rc6
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: PM-1965-Cleanup
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-12
Participants:
Linked BF Score: 166

 Description   

The critical section acquired in drop database must be cleared out on stepdown to avoid leaving the node in an inconsistent state.

In order to do that, it's possible to simply use a scoped critical section that lives as long as the coordinator is instantiated and exists the critical section on destruction.



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

Author:

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

Message: SERVER-58167 Use scoped database critical section during dropDatabase
Branch: v5.0
https://github.com/mongodb/mongo/commit/20e6f4c5018ef78c752232947398009e018c343f

Comment by Githook User [ 05/Jul/21 ]

Author:

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

Message: SERVER-58167 Use scoped database critical section during dropDatabase
Branch: master
https://github.com/mongodb/mongo/commit/36df326d54d7d97c67d9be778c70b7fcb18ef9b3

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