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

Documentation doesn't indicate that db.fsyncLock() uses counters

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Trivial - P5
    • Resolution: Duplicate
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: manual
    • Labels:
      None
    • # Replies:
      0
    • Last comment by Customer:
      true

      Description

      Multiple calls to db.fsyncLock() will require an equal number of calls to db.fsyncUnlock() to revert the database to a writable state. This is because the locks are tracked with counters, and it's not simply a boolean state (e.g. "am I locked or not").

      It would be helpful if http://docs.mongodb.org/manual/reference/method/db.fsyncLock mentioned this.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              Unassigned
              Reporter:
              jmikola Jeremy Mikola
              Participants:
              Last commenter:
              Jonathan Dahl
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Dates

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