Mongos cannot follow new primary after old one was in uninterruptible sleep state

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Cannot Reproduce
    • Priority: Major - P3
    • None
    • Affects Version/s: 4.0.23
    • Component/s: None
    • None
    • Sharding NYC
    • ALL
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      See SERVER-55486 for more details.

      The idea is that when the disk fails, the primary can spend long time without stepping down. At some point, presumably, it is moved to uninterruptible sleep state. It may or may not be related to the bug, granted. After being killed with SIGKILL the election happens, but mongos remains stuck with the old primary and never recovers unless killed.

      The behavior reproduced in 4.0, but could be present in other branches.

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

              Created:
              Updated:
              Resolved: