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

Remove unnecessary startBalancer() and stopBalancer() calls in JS tests

    XMLWordPrintableJSON

Details

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major - P3 Major - P3
    • None
    • None
    • Sharding
    • Sharding
    • ALL
    • Sharding 10 (02/19/16), Sharding 11 (03/11/16)

    Description

      Many JS tests call stopBalancer() unnecessarily because ShardingTest does it by default now. Also check that startBalancer() is not called when it could be instead specified in the ShardingTest using the enableBalancer parameter.

      This fix is important because writes to the config db do not yet support any retries, and the sharding_csrs_continuous_config_stepdown suite must blacklist tests that do not currently support command retries. Removing unnecessary writes keeps some tests in the suite.

      Attachments

        Activity

          People

            backlog-server-sharding [DO NOT USE] Backlog - Sharding Team
            dianna.hohensee@mongodb.com Dianna Hohensee (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: