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

Prevent mongod step down during moveChunk in balance_repl.js and sharding_rs2.js

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 3.2.4, 3.3.3
    • Component/s: Sharding
    • Labels:
    • Backwards Compatibility:
      Fully Compatible
    • Operating System:
      ALL
    • Backport Completed:
    • Sprint:
      Sharding 11 (03/11/16)
    • Linked BF Score:
      0

      Description

      Check if either balance_repl.js or sharding_rs2.js would be affected by making their mongod secondaries unelectable so as to prevent stepdowns. Or perhaps removing the secondaries if they are unimportant.

      The mongod stepdown is causing moveChunk to fail, and ultimately the tests to fail, in the sharding_continous_config_stepdown suite.

      From the test failures, it appears that the heartbeat is received by the primary mongod, but not executed for some time, during which time the primary decides to step down because it hasn't heard from anyone. Or the secondary doesn't hear from anyone and runs for election

        Attachments

          Issue Links

            Activity

              People

              • Votes:
                0 Vote for this issue
                Watchers:
                4 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: