-
Type: Improvement
-
Resolution: Unresolved
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
Replication
Something I noticed while analyzing work done under the ReplicationCoordinator mutex is that we signal all tailable oplog waiters while advancing the committed snapshot, which seems unnecessary and costly to do while holding the mutex. The CappedInsertNotifier already has its own mutex.
- is related to
-
SERVER-85875 Storage engine majority committed snapshot is advanced under ReplicationCoordinator mutex
- Backlog
- related to
-
SERVER-90884 Do not call opObserver methods under ReplicationCoordinator mutex.
- Open