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

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

    XMLWordPrintableJSON

Details

    • Icon: Bug Bug
    • Resolution: Cannot Reproduce
    • Icon: Major - P3 Major - P3
    • None
    • 4.0.23
    • None
    • None
    • Sharding NYC
    • ALL

    Description

      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.

      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:
            6 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: