[SERVER-33505] Watchdog probe files from multiple mongod processes may collide Created: 27/Feb/18  Updated: 05/Feb/20  Resolved: 04/Feb/20

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

Type: Improvement Priority: Major - P3
Reporter: Bruce Lucas (Inactive) Assignee: Mark Benvenuto
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Duplicate
duplicates SERVER-33479 Improve watchdog directory check logging Closed
Related
related to SERVER-33479 Improve watchdog directory check logging Closed
Sprint: Security 2019-01-27, Security 2020-02-10
Participants:
Case:

 Description   

The storage watchdog facility creates a few probe files, writes a string to them, reads it back, and terminates mongod if the read value doesn't match the written value. Probe files are created in the same directory as the auditPath and logPath files. If multiple mongod processes are running on a machine with audit files or log files in the same directory, the watchdog probe files will collide. This can cause false alarms.

This could be addressed by embedding the mongod pid in the probe file name, or by embedding the audit file or log file name in the probe file name.



 Comments   
Comment by Ramon Fernandez Marina [ 05/Feb/20 ]

I tested with 4.2 (and 4.0 should also work) and I see the pid being appended to the probe file as per SERVER-33479, which addresses the issue of having multiple mongod processes using the same logpath.

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