-
Type: Bug
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: None
-
None
-
Cluster Scalability
-
Fully Compatible
-
ALL
-
200
The "hangRemoveShardBeforeUpdatingClusterCardinalityParameter" failpoint in cluster_cardinality_parameter_interrupt.js should not be running multiversion suites because it was recently introduced in v8.1 and is not planned to be backported to earlier versions.
Wrap L160 to L195 in a clause where isMultiversion(which is defined here) is false to avoid multiversion failures.
- related to
-
SERVER-91070 Remove multiversion check in cluster_cardinality_parameter_interrupt.js when v9.0 becomes last-lts
- Backlog