[SERVER-40667] MongoD Storage watchdog should treat unexpected interruption as process-fatal Created: 16/Apr/19  Updated: 29/Oct/23  Resolved: 01/Aug/19

Status: Closed
Project: Core Server
Component/s: Internal Code
Affects Version/s: None
Fix Version/s: 4.3.1, 4.2.2

Type: Bug Priority: Major - P3
Reporter: Andy Schwerin Assignee: Mathew Robinson (Inactive)
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Backwards Compatibility: Fully Compatible
Operating System: ALL
Backport Requested:
v4.2
Sprint: Dev Tools 2019-08-12
Participants:

 Description   

The storage engine watchdog treats interruption of one of its periodic threads as fatal to that thread, but not to the process. However, it does not start a replacement thread, meaning that such an interruption (which a sufficiently powerful user can cause with a `killOp` operation) would stop monitoring, leaving behind just an error-level log message. We should change that message to severe-level (F) and terminate the process when we encounter it.



 Comments   
Comment by Githook User [ 29/Oct/19 ]

Author:

{'name': 'Ben Caimano', 'username': 'bcaimano', 'email': 'ben.caimano@mongodb.com'}

Message: SERVER-40667 MongoD Storage watchdog should treat unexpected interruption as process-fatal
Branch: v4.2
https://github.com/mongodb/mongo/commit/78d5cff07cc98d173501e7b8e61d3fd8d85e53f3

Comment by Githook User [ 31/Jul/19 ]

Author:

{'name': 'Mathew Robinson', 'email': 'chasinglogic@gmail.com', 'username': 'chasinglogic'}

Message: SERVER-40667 MongoD Storage watchdog should treat unexpected interruption as process-fatal
Branch: master
https://github.com/mongodb/mongo/commit/c6ec415752c8398f588491d8af1c54ee4e7fcbb4

Comment by Mathew Robinson (Inactive) [ 30/Jul/19 ]

Code review url: https://mongodbcr.appspot.com/490170006/

Generated at Thu Feb 08 04:55:39 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.