[SERVER-59938] Make design decision and implement health observers on/off at runtime Created: 14/Sep/21  Updated: 06/Dec/22  Resolved: 15/Sep/21

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

Type: Improvement Priority: Major - P3
Reporter: Andrew Shuvalov (Inactive) Assignee: [DO NOT USE] Backlog - Sharding NYC
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
is duplicated by SERVER-59396 Runtime configration for facet parame... Closed
Assigned Teams:
Sharding NYC
Participants:
Story Points: 3

 Description   

Preferred solution: we have a 3-state parameter for each observer "off/nonCritical/critical" that could be changed at runtime. Make sure the parameter could be made in a thread safe fashion. Then check the value on each periodic check. This should not be expensive as we run periodic check only once every 50 ms.

Important detail is that if the observer is turned off it should still do some work during the next periodic check to clear the fault state for itself.

Remember that if the manager is making the decision to not invoke observer health check at all it means the configuration cannot be changed at runtime, because then the fault state can remain "stuck" at the last run outcome.


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