-
Type: Task
-
Resolution: Unresolved
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
None
-
Replication
-
(copied to CRM)
For WT to calculate all_durable and advance the stable_timestamp, it has to walk all opened sessions. In high load scenarios and connection storms this can lead to contention on the ReplicationCoordinator mutex, slowing replication and inducing read/write concern majority lag.
- is related to
-
SERVER-84467 Add duration of how long an oplog slot is kept open to FTDC
- Open
-
SERVER-85331 Add duration taken to calculate all_durable to FTDC
- Open
- related to
-
SERVER-18934 Don't require storage engines to implement oplog visibility rules
- Backlog
-
SERVER-70155 Add duration of how long an oplog slot is kept open to mongod "Slow query" log lines
- Closed
-
SERVER-84440 Expose the number of replication waiters in serverStatus
- Closed