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

Fix waits for RSM removal in sharding/remove2.js test

    XMLWordPrintableJSON

Details

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Major - P3 Major - P3
    • 4.7.0
    • None
    • Sharding
    • None
    • Fully Compatible
    • ALL
    • Sharding 2020-06-01
    • 24

    Description

      sharding/remove2.js is waiting for the ReplicaSetMonitor timeout in order to be able re-add a shard after its removal.

      Instead of waiting 60s for the RSM to be removed from the interesting nodes, pols the connectionsPoolStats of these nodes until it is actually removed.

      The new polling approach is reducing the test execution time on Enterprise RHEL 6.2  run time form ~2:40 to ~1:40

      This commit also unblacklist  the sharding/remove2.js test from the multiversion suites. Because the new polling approach solves BF-17247.

      Attachments

        Activity

          People

            tommaso.tocci@mongodb.com Tommaso Tocci
            tommaso.tocci@mongodb.com Tommaso Tocci
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: