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

Improve journal flusher locking behavior

    XMLWordPrintable

Details

    • Improvement
    • Status: Open
    • Major - P3
    • Resolution: Unresolved
    • None
    • None
    • None
    • None
    • Execution Team 2022-10-17

    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 SERVER-65821. We should investigate ways to improve this behavior so that we can remove the workaround added in that ticket.

      Attachments

        Issue Links

          is depended on by

          Improvement - An improvement or enhancement to an existing feature or task. SERVER-66342 Remove resourceIdFeatureCompatibilityVersion

          • Major - P3 - Major loss of function.
          • Backlog
          related to

          Bug - A problem which impairs or prevents the functions of the product. SERVER-65821 Deadlock during setFCV when there are prepared transactions that have not persisted commit/abort decision

          • Critical - P2 - Crashes, loss of data, severe memory leak.
          • Closed

          Activity

            People

              matt.kneiser@mongodb.com Matt Kneiser
              gregory.noma@mongodb.com Gregory Noma
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated: