-
Type:
Task
-
Resolution: Fixed
-
Priority:
Major - P3
-
Affects Version/s: None
-
Component/s: None
-
Labels: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.
- causes
-
SERVER-90334 'hasTwoOrMoreShards' cluster parameter can be incorrect if removeShard is interrupted even if it is retried after
-
- Closed
-
- is depended on by
-
-
- Closed
-
- is related to
-
-
- Closed
-