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

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

    • Type: Icon: Task Task
    • Resolution: Duplicate
    • Priority: Icon: Critical - P2 Critical - P2
    • 01112017-cleanup
    • Affects Version/s: None
    • Component/s: manual
    • Labels:
      None

      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.

            Assignee:
            Unassigned Unassigned
            Reporter:
            bruce.lucas@mongodb.com Bruce Lucas (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved:
              9 years, 43 weeks, 4 days ago