[SERVER-39419] Stepdown interrupting a running dropDatabase command could leave unclean state Created: 07/Feb/19  Updated: 29/Oct/23  Resolved: 13/Mar/19

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

Type: Bug Priority: Major - P3
Reporter: Xiangyu Yao (Inactive) Assignee: Gregory Wlodarek
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Duplicate
is duplicated by SERVER-40730 renameCollection within dropCollectio... Closed
Related
is related to SERVER-40306 Lock acquisition in dropDatabase cmd ... Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Storage NYC 2019-03-25
Participants:
Linked BF Score: 51
Story Points: 3

 Description   

As the comment in the linked BF describes, a stepdown could interrupt a  running dropDatabase and leave the dropPending true on that database.



 Comments   
Comment by Githook User [ 13/Mar/19 ]

Author:

{'name': 'Gregory Wlodarek', 'username': 'GWlodarek', 'email': 'gregory.wlodarek@mongodb.com'}

Message: SERVER-39419 Stepdown interrupting a running dropDatabase command could leave unclean state
Branch: master
https://github.com/mongodb/mongo/commit/796ae56683f818810fa5eab8ba446c71dcf54900

Comment by Eric Milkie [ 12/Mar/19 ]

Solution will be to remove the logic check that assumes dropPending can never be true when we are about to set it to true.

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