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

The Balancer's operation context is not getting interrupted at stepdown

    • Type: Icon: Bug Bug
    • Resolution: Done
    • Priority: Icon: Major - P3 Major - P3
    • 3.3.14
    • Affects Version/s: 3.3.12
    • Component/s: Sharding
    • Labels:
      None
    • Fully Compatible
    • ALL
    • Sharding 2016-10-10
    • 0

      When a stepdown happens, the balancer's operation context is not getting marked as interrupted, which means that if it happen to wait on read concern or any other interruptible call, it will get stuck. This causes problems when that that same node is becoming primary again, because it will deadlock trying to join the already stuck balancer thread.

            Assignee:
            kaloian.manassiev@mongodb.com Kaloian Manassiev
            Reporter:
            kaloian.manassiev@mongodb.com Kaloian Manassiev
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: