[SERVER-14396] issue periodic warnings to the log while instance is locked Created: 30/Jun/14  Updated: 08/May/19  Resolved: 08/May/19

Status: Closed
Project: Core Server
Component/s: Storage
Affects Version/s: None
Fix Version/s: 4.1.11

Type: Improvement Priority: Major - P3
Reporter: Bruce Lucas (Inactive) Assignee: Gregory Wlodarek
Resolution: Done Votes: 0
Labels: RFDI, neweng
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Related
is related to DOCS-3681 warn users that fsyncUnlock needs to ... Closed
Backwards Compatibility: Fully Compatible
Sprint: Storage NYC 2019-05-20
Participants:

 Description   

For various reasons, including SERVER-1423 (which can prevent fsyncUnlock from being issued if the connection on which the fsyncLock is done is closed), or plain user error in coding scripts, a mongod instance can end up being locked unexpectedly for an extended time. When this happens the cause of the resulting symptoms can be difficult to diagnose, since the only evidence in the logs is typically an fsyncLock command, which may be far removed (e.g. in a different log file) from the time when the error is noticed.

Since mongod instance being locked for an extended time is a potentially serious condition, and is likely unintended, it would be helpful for diagnosis if periodic warnings were issued to the log, e.g. "WARNING: instance is locked; all db writes and possibly all db reads will be blocked". Such a warning possibly as often as once per minute might be justified.



 Comments   
Comment by Githook User [ 08/May/19 ]

Author:

{'email': 'gregory.wlodarek@mongodb.com', 'name': 'Gregory Wlodarek', 'username': 'GWlodarek'}

Message: SERVER-14396 Issue periodic warnings to the log while instance is locked
Branch: master
https://github.com/mongodb/mongo/commit/29db842551e2c032567406be94ba6575b5f997e2

Generated at Thu Feb 08 03:34:43 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.