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

Change addShard behavior to keep cluster parameters of the first shard

    • Type: Icon: Task Task
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 6.0.0-rc3, 6.1.0-rc0
    • Affects Version/s: None
    • Component/s: Sharding
    • Labels:
      None
    • Fully Compatible
    • v6.0
    • Sharding EMEA 2022-04-18, Sharding EMEA 2022-05-02

      SERVER-63606 introduced serialization between add/remove shard with setClusterParameters, and when adding a shard, it clears the cluster parameters of the replica set, and then send the parameters set in the config server to the shard. This is done to maintain consistency with respect of the parameters throughout the cluster.

      After some internal discussions, we would like to change the behavior to the following: we should preserve the cluster parameters of the first replica set added into the cluster and overwrite all possible values we have set on the subsequently added shards.

            Assignee:
            marcos.grillo@mongodb.com Marcos José Grillo Ramirez
            Reporter:
            marcos.grillo@mongodb.com Marcos José Grillo Ramirez
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: