[SERVER-41524] Report errors and refuse to start if the user attempts to explicitly enable the watchdog at startup with unsupported configurations Created: 04/Jun/19  Updated: 10/Jun/19  Resolved: 07/Jun/19

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

Type: New Feature Priority: Major - P3
Reporter: Sara Williamson Assignee: Mark Benvenuto
Resolution: Won't Fix Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Documented
Sprint: Security 2019-06-17
Participants:

 Description   

The only supported configurations are:

  • Storage engine is wiredTiger
  • Journaling enabled
  • Directory-per-db is not in use
  • Logging and auditing to files or stdout


 Comments   
Comment by Mark Benvenuto [ 07/Jun/19 ]

Per schwerin, closing this ticket as 'Won't Fix'.

Comment by Andy Schwerin [ 05/Jun/19 ]

Yeah, it's OK by me. There's an outside chance we get a confused call from a customer running directory-per-db because the watchdog didn't watch all their volumes, but we can deal with that via human interaction. We should make sure the documentation indicates the limitation wrt directory-per-db and close this ticket.

Comment by Mark Benvenuto [ 05/Jun/19 ]

alyson.cabral, schwerin during our 6-six week review, we came across a goal in the "Move Storage Node Watchdog to community" scope that said the watchdog should be restricted to only a specific configuration. I would prefer not to add additional restrictions on the watchdog since it is more work to add them. Adding these restrictions would break existing customers using the watchdog for instance. Also, given that the watchdog is opt-in instead of enabled by default (which we considered during scoping), I think there is no need to restrict when it can be enabled by customers. Is it ok to close this ticket as "Won't Fix"?

  1. Watchdog already supports non-wiredtiger. There is a test for in-memory for instance.
  2. Journaling is optional and the watchdog only watchs the journal if journaling is enabled.
  3. Directory Per DB - it is irrelevant to the watchdog if directory-per-db is on. If users move databases to other volumes and replace the directories with symlinks, the watchdog will miss those alternate volumes though.
  4. logging and auditing are only considered if they output to a directory, they are ignored otherwise. This conditional logic already exists in the watchdog.
Generated at Thu Feb 08 04:57:58 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.