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

Fault keeps a timer from the moment any facet entered a fault state

    XMLWordPrintable

Details

    • Task
    • Status: Closed
    • Major - P3
    • Resolution: Duplicate
    • None
    • None
    • None
    • None

    Description

      Also see SERVER-59382.

      We should track time from the moment any facet entered the critical state (severity >= 1). We count kActiveFaultDuration timeout from this moment, and we enter the ActiveFault state once this timeout is exceeded and during this period at least one facet was in critical state every time we do a periodic check.

       

      Attachments

        Issue Links

          Activity

            People

              backlog-server-sharding-nyc Backlog - Sharding NYC
              andrew.shuvalov@mongodb.com Andrew Shuvalov
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: