remove global lock from repairDatabase command

XMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Won't Fix
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Concurrency
    • Storage Execution
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      Currently the repairDatabase command takes a global lock, see this code line.

      I couldn't find a ticket to track the request to downgrade this to a database level lock, so here it is.

      There is a comment referencing SERVER-4328 (db locking) that this is a "TODO" but currently the global lock "may" be necessary due to calling syncDataAndTruncateJournal.

      After the storage changes we need to review if a downgrade to a db lock is an option. This would make repairs on a database much easier to handle from an operations point of view.

            Assignee:
            [DO NOT USE] Backlog - Storage Execution Team
            Reporter:
            Thomas Rueckstiess (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            8 Start watching this issue

              Created:
              Updated:
              Resolved: