-
Type: Bug
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: Replication
-
Fully Compatible
-
ALL
-
Repl 2017-11-13
-
0
After waiting for all collection drops to replicate to a majority of the replica set, the dropDatabase command reacquires the global lock before completing the rest of the database drop and logging the dropDatabase oplog entry. It is possible that the primary has stepped down while waiting for the collection drops. We should check ReplicationCoordinator::canAcceptWritesFor after reacquiring the global lock to avoid hitting a fatal assertion in logOp() in this case.
- is related to
-
SERVER-29874 Two Phase Drops: dropDatabase does not work with applyOps
- Closed
-
SERVER-29876 Two Phase Drops: dropDatabase should always wait for pending collection drops to complete
- Closed
-
SERVER-29277 Two Phase Drops: implement dropDatabase changes to support 2-phase drops
- Closed
- related to
-
SERVER-32402 dropDatabase after step down can cause fassert
- Closed