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

Update hasTwoOrMoreShards cluster parameter when second shard is removed from the cluster

    • Type: Icon: Task Task
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 7.3.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Fully Compatible
    • Cluster Scalability 2023-11-13
    • 57

      In SERVER-75126, we made the configsvr primary set the cluster server parameter ShardedClusterCardinalityParam.hasTwoOrMoreShards to true when the second shard is added. But we didn't make it set the parameter back to false when the cluster becomes single-shard again. One of the goals of PM-2935 is to allow a user who scales their cluster down from multi-shard to single-shard cluster to be able to use the replica set connection string to connect to their cluster so this requires the parameter to be set back to false when the second shard is removed.

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

              Created:
              Updated:
              Resolved: