[DOCS-13701] Investigate changes in SERVER-46726: Provide separate setParameter to disable diagnostic work Created: 10/Jun/20  Updated: 13/Nov/23  Due: 30/Apr/21  Resolved: 30/Apr/21

Status: Closed
Project: Documentation
Component/s: manual, Server
Affects Version/s: None
Fix Version/s: 4.4.1, 4.7.0, Server_Docs_20231030, Server_Docs_20231106, Server_Docs_20231105, Server_Docs_20231113

Type: Task Priority: Major - P3
Reporter: Backlog - Core Eng Program Management Team Assignee: Andrew Feierabend (Inactive)
Resolution: Works as Designed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Documented
documents SERVER-46726 Provide separate setParameter to disa... Closed
Participants:
Days since reply: 3 years, 35 weeks ago
Epic Link: DOCSP-9747
Story Points: 2

 Description   

Description

Downstream Change Summary

This patch introduces a new server parameter (i.e., testingDiagnosticsEnabled) for mongod and mongos that controls passive testing behavior. This option is for test purposes only, is disabled by default, and should never be used in production.

Description of Linked Ticket

We currently use enableTestCommands to enable diagnostic work and loosened permissions. This has an unfortunate side effect where sys-perf notices our non-production diagnostics. The path of least impact is an additional flag that enables "passive" testing behavior in addition to the "active" test commands.

Note to server developers: moving forward, the new API for testing diagnostics (i.e., TestingProctor) must be used for any passive testing and diagnostics work (e.g., see latch analyzer for reference). Test commands (i.e., getTestCommandsEnabled) should only be used for registering test commands and anything related to the execution of test commands and fail-points. This enables separately controlling test commands and testing diagnostics.

Scope of changes

Impact to Other Docs

MVP (Work and Date)

Resources (Scope or Design Docs, Invision, etc.)


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