The compact command should not block oplog application

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Fixed
    • Priority: Major - P3
    • 4.4.17, 5.0.12, 6.0.2, 6.1.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Fully Compatible
    • v6.0, v5.0, v4.4
    • Execution Team 2022-08-22
    • 135
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      We first take the collection exclusive lock and downgrade it to an intent lock if the storage engine supports online compaction. We should reverse the order of this as it reports confusing FTDC metrics. Start with the intent lock and upgrade to an exclusive lock if online compaction is not supported.

      I also don't think the compact command should take the PBWM lock as the command is internal to the storage engine and should not block oplog application.

              Assignee:
              Gregory Wlodarek
              Reporter:
              Gregory Wlodarek
              Votes:
              0 Vote for this issue
              Watchers:
              10 Start watching this issue

                Created:
                Updated:
                Resolved: