[SERVER-84449] High load can cause replication lag leads to write latency Created: 29/Dec/23  Updated: 02/Feb/24

Status: Open
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Major - P3
Reporter: Moustafa Maher Assignee: Backlog - Replication Team
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to SERVER-18934 Don't require storage engines to impl... Backlog
related to SERVER-70155 Add duration of how long an oplog slo... Closed
related to SERVER-84440 Expose the number of replication wait... Closed
is related to SERVER-84467 Add duration of how long an oplog slo... Open
is related to SERVER-85331 Add duration taken to calculate all_d... Open
Assigned Teams:
Replication
Participants:
Case:

 Description   

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.


Generated at Thu Feb 08 06:55:03 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.