Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-66341

Improve journal flusher locking behavior

    • Type: Icon: Improvement Improvement
    • Resolution: Duplicate
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • Catalog and Routing
    • Execution Team 2022-10-17, CAR Team 2023-12-25
    • 3

      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.

            Assignee:
            josef.ahmad@mongodb.com Josef Ahmad
            Reporter:
            gregory.noma@mongodb.com Gregory Noma
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: