-
Type:
Improvement
-
Resolution: Duplicate
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
Catalog and Routing
-
Execution Team 2022-10-17, CAR Team 2023-12-25
-
3
-
None
-
3
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Currently the journal flusher runs on its own thread and performs a few actions, including updating the oplog truncation point document. This particular action means that the journal flusher has to take global/db/collection locks, which can be problematic as seen in SERVER-65821. We should investigate ways to improve this behavior so that we can remove the workaround added in that ticket.
- duplicates
-
-
- Closed
-
- is depended on by
-
-
- Closed
-
- is related to
-
-
- Closed
-
- related to
-
SERVER-65821 Deadlock during setFCV when there are prepared transactions that have not persisted commit/abort decision
-
- Closed
-