-
Type: Task
-
Resolution: Won't Do
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
None
-
Cluster Scalability 2024-2-19
- Running transitionToDedicatedCluster or addShard command would cause the replica set endpoint to become inactive (since the replica set endpoint is supported only on a single-sharded cluster with embedded config servers). So it causes the checkMetadataConsistency commands in the CheckMetadataConsistencyInBackground hook to fail with CommandNotFound since the replica set connection would no longer support sharding commands.
- Running convertToCapped or cloneCollectionAsCapped command currently leads to inconsistent metadata when featureFlagTrackUnshardedCollectionsOnShardingCatalog is enabled (see
SERVER-86360) so we should extend the code added inSERVER-86030to make jstestfuzz skip these commands when testing replica set endpoint. - Running getClusterParameter currently causes issue as described in
SERVER-86440.
- is depended on by
-
SERVER-86285 Add jstestfuzz_replication suite with autobootstrap and replica set endpoint
- Closed
-
SERVER-86286 Add jstestfuzz_sharded suite with replica set endpoint
- Closed