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

Wait for RSM to detect failover in range_deleter_interacts_correctly_with_refine_shard_key.js

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 4.4.0-rc7, 4.7.0
    • Affects Version/s: None
    • Component/s: Sharding
    • Labels:
      None
    • Fully Compatible
    • ALL
    • v4.4
    • 49

      range_deleter_interacts_correctly_with_refine_shard_key.js steps up a new primary and then creates an index through a mongos right after. If the router's RSM is not using the streamable protocol, it may have a stale view of the primary and the createIndexes will target the old primary and fail with NotMaster. To support the non-streamable protocols, the test should wait for the router's RSM to detect the new primary before creating the index.

            Assignee:
            jack.mulrow@mongodb.com Jack Mulrow
            Reporter:
            jack.mulrow@mongodb.com Jack Mulrow
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: