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

Make post shard removal safety checks robust to failovers

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 8.1.0-rc0, 8.0.0-rc7
    • Affects Version/s: None
    • Component/s: None
    • None
    • Cluster Scalability
    • Fully Compatible
    • ALL
    • v8.0
    • Cluster Scalability 2024-6-10
    • 200

      SERVER-90224 added safety checks that run in the background config shard transition thread after removing the config server as a shard. In suites with failovers, the checks can fail in the following ways:

      1. Throwing a "retryable" error if a node being read from is killed
      2. Waiting for an optime indefinitely if the term of the chosen optime was superseded

            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: