-
Type: Task
-
Resolution: Duplicate
-
Priority: Critical - P2
-
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.
- duplicates
-
DOCS-1603 Warn that fsyncLock() may prevent being able to log into shell to fsyncUnlock()
- Closed
- is related to
-
SERVER-1423 reads often aren't possible while in fsync and lock mode
- Closed
- related to
-
SERVER-14396 issue periodic warnings to the log while instance is locked
- Closed