Make the _shardsvrJoinDDLCoordinators command resilient to FailedToSatisfyReadPreference exception

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major - P3
    • 8.1.0-rc0, 8.0.0-rc10
    • Affects Version/s: 8.0.0-rc6
    • Component/s: None
    • None
    • Catalog and Routing
    • Fully Compatible
    • ALL
    • v8.0
    • CAR Team 2024-06-24, CAR Team 2024-07-08
    • 200
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      As a part of add / remove shard, we send the _shardsvrJoinDDLCoordinators command to all shards in the cluster with a read preference set to primary.

      If any of these fail due to a FailedToSatisfyReadPreference exception, we will fail the overall add / remove shard command.

      BF-33560 shows that if we have continuous stepdown running, we could get to a state where a replica set does not have an active primary and we receive this response when running the _shardsvrJoinDDLCoordinators command against the cluster.

       

            Assignee:
            Marcos José Grillo Ramirez
            Reporter:
            Ben Gawel
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: