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

Remove and re-add shard test wait time is inconsistent with registry refresh timeout

XMLWordPrintableJSON

    • Type: Icon: Bug Bug
    • Resolution: Won't Fix
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Sharding
    • None
    • Sharding
    • ALL
    • Hide

      1. Run jstests/sharding/remove2.js test until it fails.

      Show
      1. Run jstests/sharding/remove2.js test until it fails.
    • Sharding 2019-12-16, Sharding 2019-12-30, Sharding 2020-01-13, Sharding 2020-01-27, Sharding 2020-02-10, Sharding 2020-02-24, Sharding 2020-03-09, Sharding 2020-03-23, Sharding 2020-04-06, Sharding 2020-04-20
    • 19

      The remove2.js test waits for 20 seconds hoping that the replica set monitor timeouts and refreshes other shard information, however the timeout for the registry is 30 seconds. This test should wait until the registry is successfully updated with the new shard information.

            Assignee:
            backlog-server-sharding [DO NOT USE] Backlog - Sharding Team
            Reporter:
            marcos.grillo@mongodb.com Marcos José Grillo Ramirez
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: