-
Type:
Improvement
-
Resolution: Unresolved
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
None
-
Replication
-
Repl 2026-10-12
-
None
-
None
-
None
-
None
-
None
-
None
-
None
In HELP-99223, we could see that replication lag was building, but could not understand why that was (see also SERVER-134905). We should ensure that metrics are sufficient to do a reasonably confident RCA based on FTDC data.
Specifically, we should be able to differentiate between the fetcher, writer, and applier being the bottleneck. We should also be able to understand how many threads are active in each of these, and what they are spending their time doing (e.g. blocked by backpressure, blocked in storage, idle).
- is related to
-
SERVER-134905 Investigate why secondaries were unable to keep up with primary workload
-
- Closed
-
- related to
-
SERVER-134234 Investigate improvements to OplogWriter for large oplog entries
-
- Investigating
-