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

Resmoke should stop the balancer before shutting down sharded clusters

    XMLWordPrintable

    Details

    • Backwards Compatibility:
      Fully Compatible
    • Operating System:
      ALL
    • Backport Requested:
      v3.6
    • Sprint:
      TIG 2018-06-04
    • Linked BF Score:
      0

      Description

      This has always been an issue but we seemingly have never inserted enough data to keep the balancer busy until the nodes shut down. Now with SERVER-34555 doing heavier workloads on resmoke clusters, we've started to run into this problem.

      We should have ShardedClusterFixture stop the balancer as part of its teardown process.

        Attachments

          Issue Links

          causes

          Bug - A problem which impairs or prevents the functions of the product. SERVER-36449 ShardedClusterFixture tries to access never started mongos

          • Minor - P4 - Minor loss of function, or other problem where easy workaround is present.
          • Open
          is depended on by

          Task - A task that needs to be done. SERVER-34555 Migrate concurrency_sharded_with_stepdowns{,_and_balancer}.yml test suites to run directly via resmoke.py

          • Major - P3 - Major loss of function.
          • Closed

            Activity

              People

              Assignee:
              jonathan.abrahams Jonathan Abrahams
              Reporter:
              robert.guo Robert Guo
              Participants:
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: