-
Type: Improvement
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: Replication
-
None
-
Fully Compatible
-
Repl 2018-04-23
-
13
Waiting for the drop command gets replicated to a majority doesn't guarantee the drop completes on the primary, so after the command returns, the drop-pending collection reaper will actually drop the collection, which takes the database lock in X mode. The asynchronous DB lock in X mode may be unexpected to users, especially transaction users, because it will block (or abort when SERVER-33244 is done) transactions waiting for the DB lock.
- is depended on by
-
SERVER-33244 Make all lock acquisitions for transactions have 0 second timeout
- Closed
- is duplicated by
-
SERVER-35613 Two-phase drop can prevent subsequent transaction from acquiring locks.
- Closed
- is related to
-
SERVER-38744 w:majority collection drops may try to acquire database X lock after completing successfully
- Closed
-
SERVER-34069 Postpone 2nd phase of collection drop until drop timestamp is in the stable checkpoint
- Closed
-
SERVER-34452 Wait for 2-phase drop to finish in transaction tests
- Closed
- related to
-
SERVER-34349 Wait for drop to be majority committed in transaction tests
- Closed
-
SERVER-34717 Performance regression in dropDatabase
- Closed