-
Type:
Bug
-
Resolution: Gone away
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: Replication
-
Replication
-
ALL
-
Repl 2017-10-02, Repl 2017-10-23
The append oplog note command relies on the command subsystem to prevent it from running when it's a secondary, but that check is inherently racy as it's not holding any db locks at that point.
Also, the appendOplogNote command currently takes a global write lock, which is unnecessary heavy.
The command should be changed to take the global lock in mode IX, check that it's still primary, and then proceed with calling onOpMessage to write the no-op oplog entry (which takes a write lock on the oplog internally).
- duplicates
-
SERVER-27772 processing afterClusterTime > clusterTime on secondary
-
- Closed
-
- is related to
-
-
- Closed
-
-
SERVER-12119 Add new command to allow applications to append notes to the oplog.
-
- Closed
-