[SERVER-82713] Consider preventing external users from setting "shardedClusterCardinalityForDirectConns" cluster parameter Created: 02/Nov/23  Updated: 09/Nov/23

Status: Backlog
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Major - P3
Reporter: Cheahuychou Mao Assignee: Backlog - Catalog and Routing
Resolution: Unresolved Votes: 0
Labels: car-qw
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Assigned Teams:
Catalog and Routing
Participants:
Story Points: 1

 Description   

This cluster parameter consists of a "hasTwoOrMoreShards" boolean which must be set and unset atomically with add/remove shard operation. It should reflect the real cardinality of the cluster so shouldn't be settable by external users (unless we think that admin users might need to set it manually if this parameter somehow has incorrect value due to a bug). Currently, this cluster parameter is not documented, so no users should know about it and try to set it. But if we decide to do this ticket, a uassert to prevent this cluster parameter might be needed since currently there isn't a way to specify a cluster parameter as internal-only,


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