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

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

XMLWordPrintableJSON

    • Type: Icon: Bug Bug
    • Resolution: Duplicate
    • Priority: Icon: Trivial - P5 Trivial - P5
    • Server_Docs_20231030
    • Affects Version/s: None
    • Component/s: manual
    • Labels:
      None

      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.

            Assignee:
            Unassigned Unassigned
            Reporter:
            jmikola@mongodb.com Jeremy Mikola
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved:
              11 years, 3 weeks, 3 days ago