[SERVER-43458] Remove TempRelease in dropDatabase Created: 23/Sep/19  Updated: 06/Dec/22  Resolved: 22/Nov/21

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

Type: Task Priority: Major - P3
Reporter: PM Bot Assignee: Backlog - Storage Execution Team
Resolution: Done Votes: 0
Labels: autogen-todo
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
is duplicated by SERVER-59750 Clean up todo of TempRelease in dropD... Closed
Related
is related to SERVER-29874 Two Phase Drops: dropDatabase does no... Closed
is related to SERVER-29802 Non-atomic applyOps command should no... Closed
is related to SERVER-49866 Remove TempRelease Closed
Assigned Teams:
Storage Execution
Participants:

 Description   

Complete TODO listed in SERVER-29802



 Comments   
Comment by Judah Schvimer [ 16/Oct/19 ]

The TODO here is the following:

        // TODO: Remove the use of this TempRelease object when SERVER-29802 is completed.
        // The work in SERVER-29802 will adjust the locking rules around applyOps operations and
        // dropDatabase is expected to be one of the operations where we expect to no longer acquire
        // the global lock.
        Lock::TempRelease release(opCtx->lockState());

Sending to Execution since I don't know if this TODO is no longer true or if this TempRelease can be removed.

Comment by Benety Goh [ 26/Sep/19 ]

TODO comment was added during SERVER-29874

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