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

Handle replica set config error in shard split fixture

    XMLWordPrintableJSON

Details

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Major - P3 Major - P3
    • 7.1.0-rc0
    • None
    • None
    • None
    • Serverless
    • Fully Compatible
    • ALL
    • v7.0
    • Server Serverless 2023-05-15
    • 20

    Description

      When we remove recipient nodes in the shard split fixture we might have an error in `replSetReconfig`. We can retry the reconfig as we use `with_naive_retry` but we do not fetch an updated config from the primary because replSetGetConfig is in a separate retry loop. This can lead a situation we can't escape from (if the config we try to apply is state).

      Instead, in case of issue, we need to fetch the new primary, fetch the most recent config and reconfig using it.

      Attachments

        Activity

          People

            didier.nadeau@mongodb.com Didier Nadeau
            didier.nadeau@mongodb.com Didier Nadeau
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: