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

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 4.5.1, 4.4.0-rc7
    • Component/s: Sharding
    • Labels:
      None
    • Backwards Compatibility:
      Fully Compatible
    • Operating System:
      ALL
    • Backport Requested:
      v4.4
    • Linked BF Score:
      49

      Description

      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.

        Attachments

          Issue Links

            Activity

              People

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

                Dates

                Created:
                Updated:
                Resolved: