Details
-
Bug
-
Resolution: Fixed
-
Major - P3
-
None
-
None
-
Fully Compatible
-
ALL
-
Repl 2018-01-01, Repl 2018-01-15
-
0
Description
If there is a step down, we return early and fail, but we never take the database out of the "drop pending" state. Thus if a new dropDatabase oplog entry comes in after the step down, it can cause an error in oplog application and a crash.
Attachments
Issue Links
- is related to
-
SERVER-31436 dropDatabase must check `ReplicationCoordinator::canAcceptWritesFor` after reacquiring global lock
-
- Closed
-