[SERVER-66341] Improve journal flusher locking behavior Created: 10/May/22 Updated: 14/Dec/23 Resolved: 14/Dec/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Gregory Noma | Assignee: | Josef Ahmad |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | car-qw | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||||||||||
| Assigned Teams: |
Catalog and Routing
|
||||||||||||||||||||||||||||
| Sprint: | Execution Team 2022-10-17, CAR Team 2023-12-25 | ||||||||||||||||||||||||||||
| Participants: | |||||||||||||||||||||||||||||
| Story Points: | 3 | ||||||||||||||||||||||||||||
| Description |
|
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 |
| Comments |
| Comment by Josef Ahmad [ 14/Dec/23 ] |
|
Closing as a duplicate of |