[SERVER-81974] Update hasTwoOrMoreShards cluster parameter when second shard is removed from the cluster Created: 09/Oct/23  Updated: 21/Nov/23  Resolved: 09/Nov/23

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 7.3.0-rc0

Type: Task Priority: Major - P3
Reporter: Cheahuychou Mao Assignee: Cheahuychou Mao
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
is depended on by SERVER-81968 Make mongod dispatch commands through... Closed
Related
is related to SERVER-75126 Update cluster parameter when second ... Closed
Backwards Compatibility: Fully Compatible
Sprint: Cluster Scalability 2023-11-13
Participants:
Linked BF Score: 57

 Description   

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.



 Comments   
Comment by Githook User [ 09/Nov/23 ]

Author:

{'name': 'Cheahuychou Mao', 'email': 'cheahuychou.mao@mongodb.com', 'username': 'cheahuychou'}

Message: SERVER-81974 Update hasTwoOrMoreShards cluster parameter when second shard is removed from the cluster
Branch: master
https://github.com/mongodb/mongo/commit/cae1fcae223b81af52c41249e13d30c68fbba3fd

Generated at Thu Feb 08 06:47:53 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.