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

XMLWordPrintableJSON

    • Type: Icon: Task Task
    • Resolution: Duplicate
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • Labels:
      None
    • Sharding NYC

      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.

       

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

              Created:
              Updated:
              Resolved: