[DOCS-3681] warn users that fsyncUnlock needs to be issued on same connection as fsyncLock Created: 30/Jun/14  Updated: 11/Jan/17  Resolved: 01/Jul/14

Status: Closed
Project: Documentation
Component/s: manual
Affects Version/s: None
Fix Version/s: 01112017-cleanup

Type: Task Priority: Critical - P2
Reporter: Bruce Lucas (Inactive) Assignee: Unassigned
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Duplicate
duplicates DOCS-1603 Warn that fsyncLock() may prevent bei... Closed
Related
related to SERVER-14396 issue periodic warnings to the log wh... Closed
is related to SERVER-1423 reads often aren't possible while in ... Closed
Participants:
Days since reply: 9 years, 33 weeks, 2 days ago

 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.


Generated at Thu Feb 08 07:46:16 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.