-
Type:
Task
-
Resolution: Fixed
-
Priority:
Major - P3
-
Affects Version/s: None
-
Component/s: None
-
Cluster Scalability
-
Fully Compatible
-
ClusterScalability 30Mar-13Apr, ClusterScalability 13Apr-27Apr
-
200
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Currently, the behavior of the resharding coordinator is sensitive to the cluster’s active FCV. This sensitivity makes it harder to ensure correctness during rolling upgrades or downgrades. To address this, the resharding coordinator should maintain a fixed and stable view of the FCV throughout the entire lifetime of a resharding operation.
Adopt the same pattern CAR uses for long-lived DDL coordinators: capture and persist a VersionContext at coordinator initialization and then use it to fix the coordinator’s view of FCV for the duration of the operation, regardless of subsequent FCV changes.
- related to
-
SERVER-104789 Make random_ddl_setFCV_operations_with_metadata_check.js also run in config shard variants
-
- Closed
-
-
SERVER-92437 Problems with resharding operation that starts while the FCV is "8.0" or "7.3" and commits while the FCV is "Downgrading to 7.0"
-
- Needs Scheduling
-
-
SERVER-127574 Write setFCV upgrade/downgrade test with pinned resharding version
-
- Closed
-