Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-59938

Make design decision and implement health observers on/off at runtime

    XMLWordPrintableJSON

Details

    • Icon: Improvement Improvement
    • Resolution: Duplicate
    • Icon: Major - P3 Major - P3
    • None
    • None
    • None
    • None
    • Sharding NYC
    • 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.

      Attachments

        Activity

          People

            backlog-server-sharding-nyc [DO NOT USE] Backlog - Sharding NYC
            andrew.shuvalov@mongodb.com Andrew Shuvalov (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: