Uploaded image for project: 'Documentation'
  1. Documentation
  2. DOCS-3838

unclear locking behavior when repairing a database

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: v1.3.10
    • Component/s: manual
    • Labels:
      None
    • Last comment by Customer:
      true
    • Actual Time:
      8

      Description

      The documentation on locking during a database repair is ambiguous.

      http://docs.mongodb.org/manual/reference/command/repairDatabase/

      The command documentation implies a global lock is obtained. This alone is unclear because it's not obvious if this was updated after per-database locks were implemented.

      To clear up confusion, a user may find themselves on this page, which very strongly implies that repairing a database will only hold the lock on the database being repaired, not the "database" as in the whole process.

      http://docs.mongodb.org/manual/faq/concurrency/#which-administrative-commands-lock-the-database

      I just attempted to repair a database on a 2.6 replica set secondary and all operations across all databases were blocked.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              tim.slavin Tim Slavin
              Reporter:
              aaron.westendorf Aaron Westendorf
              Participants:
              Last commenter:
              Jonathan Dahl Jonathan Dahl
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:
                Days since reply:
                7 years, 9 weeks ago
                Date of 1st Reply: