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

fsyncLock/Unlock pages should warn about nested calls to fsyncLock

    XMLWordPrintable

    Details

    • Type: Task
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Duplicate
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: manual
    • Labels:
      None
    • # Replies:
      0
    • Last comment by Customer:
      false

      Description

      Calling fsyncLock multiple times without calling fsyncUnlock in between can cause a race condition and block a node until the process is restarted, see SERVER-6302.

      Until the bug is fixed, users should be warned in the documentation for fsyncLock and fsyncUnlock that this can happen and advise against calling fsyncLock repeatedly. A work-around (inspecting if a node is locked before locking) is given on the server ticket.

      A common use case is to run automated backup scripts repeatedly (e.g. cron jobs). If the backup doesn't finish before the next one is scheduled, these kinds of nested calls can happen.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              Unassigned
              Reporter:
              thomasr Thomas Rueckstiess
              Participants:
              Last commenter:
              Jonathan Dahl
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:
                Days since reply:
                7 years, 18 weeks, 1 day ago