-
Type: Bug
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: 7.0.1, 8.0.0-rc0, 7.3.0
-
Component/s: None
-
None
-
Catalog and Routing
-
Fully Compatible
-
ALL
-
v8.0
-
CAR Team 2024-08-05, CAR Team 2024-08-19
Today, we have three different server parameters defined in sharding_cluster_parameters.idl. These are: shardedClusterCardinalityForDirectConns, addOrRemoveShardInProgress, and configServerReadPreferenceForCatalogQueries.
If we try to run getClusterParameter via the MongoS
db.adminCommand({ getClusterParameter: 'addOrRemoveShardInProgress' })
we will encounter an error, such as:
(MongoServerError[NoSuchKey]: Unknown server parameter: addOrRemoveShardInProgress
It happens the same if we try to update the cluster parameter (setClusterParameter) with a new value.
The root cause of this problem is that sharding_cluster_parameters.idl is only linked in MongoD, not in MongoS.
- is related to
-
SERVER-91294 Make config queries use a primaryPreferred read preference in clusters with a config shard
- Closed
- related to
-
SERVER-93425 Validate that all cluster server parameters are linked in both MongoD and MongoS
- Backlog