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

'hasTwoOrMoreShards' cluster parameter can be incorrect if removeShard is interrupted even if it is retried after

XMLWordPrintableJSON

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 8.1.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • Labels:
      None
    • Cluster Scalability
    • Fully Compatible
    • ALL
    • Cluster Scalability 2024-5-27

      The last step of removeShard in 8.1+ is updating the "hasTwoOrMoreShards" cluster parameter if the number of shards goes from 2 back to 1. If there is an interrupt before that step, the "hasTwoOrMoreShards" cluster parameter would be left as true even if there is a retry because the retry would fail with ShardNotFound here and never get to the cluster parameter update step. 

            Assignee:
            cheahuychou.mao@mongodb.com Cheahuychou Mao
            Reporter:
            cheahuychou.mao@mongodb.com Cheahuychou Mao
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: