[SERVER-33566] `restartCatalog` can race with `dropDatabase` Created: 01/Mar/18  Updated: 29/Oct/23  Resolved: 13/Mar/18

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

Type: Bug Priority: Major - P3
Reporter: Daniel Gottlieb (Inactive) Assignee: Kyle Suarez
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Related
related to SERVER-32989 `repairDatabase` can race with `dropD... Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Repl 2018-03-26
Participants:
Linked BF Score: 0

 Description   

Same as SERVER-32989 but replace `repairDatabase` with `restartCatalog`.



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

Author:

{'email': 'kyle.suarez@mongodb.com', 'name': 'Kyle Suarez', 'username': 'ksuarz'}

Message: SERVER-33566 fail restartCatalog if any databases are drop-pending
Branch: master
https://github.com/mongodb/mongo/commit/9580cd1b3e795a9833b53eab5382827421fcca74

Comment by Kyle Suarez [ 01/Mar/18 ]

Should we simply fail a restartCatalog command with the MongoDB equivalent of EAGAIN if any of the databases are drop-pending?

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