Loading...

XML

Word

Printable

JSON

Type: Bug
Resolution: Fixed
Priority: Major - P3
Fix Version/s: 3.6.3, 3.7.1
Affects Version/s: None
Component/s: Replication
Labels:
None

Backwards Compatibility:
Fully Compatible
Operating System:
ALL
Sprint:
Repl 2018-01-01, Repl 2018-01-15
Linked BF Score:
0
Confidence Status:
None
Work Order:
3
CAR Domain/s:
None

Aha! Reference:
None
Tracking Level:
None
Risk Status:
None
Exec Notes:
None
Goal Name(s):
None
Goal Link:
None

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.

is related to

SERVER-31436 dropDatabase must check `ReplicationCoordinator::canAcceptWritesFor` after reacquiring global lock

Closed

Assignee:: Benety Goh
Reporter:: Judah Schvimer
Participants:: Benety Goh, Githook User, Judah Schvimer
Votes:: 0 Vote for this issue
Watchers:: 4 Start watching this issue

Created:: Dec 19 2017 03:26:20 PM UTC
Updated:: Oct 30 2023 11:09:48 PM UTC
Resolved:: Jan 03 2018 09:35:28 PM UTC

Details

Description

Attachments

Issue Links

Activity

People

Dates