Use new device mapper testing facility to reproduce primary disk outage

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Won't Fix
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • Sharding NYC
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      This depends on SERVER-55486 and is reproducing production outage:

      1. Primary mongod has disk failure
      2. No failover happens
      3. Kill primary with sigkill
      4. Mongos is unable to detect the failover

            Assignee:
            [DO NOT USE] Backlog - Sharding NYC
            Reporter:
            Andrew Shuvalov (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: