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

3.4: Clarify multiple fsyncLock behavior

    XMLWordPrintable

    Details

    • Type: Task
    • Status: Closed
    • Priority: Critical - P2
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: None
    • Labels:
      None
    • # Replies:
      4
    • Last comment by Customer:
      true
    • Story Points:
      1
    • Sprint:
      KANBAN BUCKET

      Description

      Documentation Changes
      • Clarify that fsyncLock/fsyncUnlock tracks the number of open fsyncLocks. For example, fsyncLock(); fsyncLock(); fsyncUnlock(); stays locked.
      • Document lockCount field of return document.
      Description

      Currently (and historically) users could call fsyncLock multiple times which would then require the same number of fsyncUnlock calls to unlock the mongod instance. We should make this behavior clear in both our fsyncLock and fsyncUnlock documentation. I would recommend changing just for 3.4 as there exists a race condition that makes multiple lock/unlock unsafe prior to 3.4 (see SERVER-6302).

      Additionally, with the fix for SERVER-6302 in 3.4 we added a "lockCount" field to the fsyncLock / fsyncUnlock result documents. This field contains the lock count after executing the command. In the fsyncUnlock case, a lockCount of "0" means the lock has been released and mongod can accept writes. We should reference this field and behavior in our documentation.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              kay.kim Kay Kim (Inactive)
              Reporter:
              james.wahlin James Wahlin
              Participants:
              Last commenter:
              Kay Kim (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Dates

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