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

warn users that fsyncUnlock needs to be issued on same connection as fsyncLock

    XMLWordPrintable

    Details

    • Type: Task
    • Status: Closed
    • Priority: Critical - P2
    • Resolution: Duplicate
    • Affects Version/s: None
    • Fix Version/s: 01112017-cleanup
    • Component/s: manual
    • Labels:
      None
    • # Replies:
      0
    • Last comment by Customer:
      true
    • Actual Time:
      8

      Description

      Because of SERVER-1423, once the instance is fsyncLocked, it may not be possible to log in again until it is unlocked. So if the db connection on which fsyncLock is issued is closed, the instance may be permanently hung with no ability to log to unlock the instance or shut it down, and no recourse but to kill -9 the mongod process. Therefore it is vital that when fsyncLock is issued, the db connection on which it is issued should be kept open for a subsequent fsyncUnlock.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              Unassigned
              Reporter:
              bruce.lucas Bruce Lucas
              Participants:
              Last commenter:
              Jonathan Dahl
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:
                Days since reply:
                6 years, 12 weeks, 5 days ago