-
Type:
Task
-
Resolution: Unresolved
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
None
-
Catalog and Routing
-
None
-
None
-
None
-
None
-
None
-
None
-
None
In SPM-3830 we made so that during upgrade to FCV 9.0 timeseries collections will be converted automatically to viewless timeseries . The conversion will start after the cluster (including the config server) have already transitioned to FCV 9.0 and before the setFeatureComatibilityVersion command returns the response to the user. This means that if the conversion is interrupted by an error (e.g. network error, primary stepdown etc..) it will be the responsibility of the user or automation agent to keep retrying the setFeatureComatibilityVersion command until it will finally succeed. If the user won’t retry the operation interrupted during this phase, the cluster will remain in FCV 9.0 fully upgraded state but possibly with some legacy timeseries collections. (known setFCV limiration SERVER-106164).
The goal of this ticket is to implement a precondition check before upgrading to any FCV > 9.0 (e.g. 9.1.x or 10.0.x) to prevent the upgrade in case the cluster still contains legacy timeseries collections because it didn't fully complete the previous FCV transition.
The check only need to check for the presence of collections prefixed with `system.buckets.`
- is related to
-
SERVER-106164 Add guardrails to ensure FCV upgrades/downgrades are finalized
-
- Backlog
-
- related to
-
SERVER-113458 CheckMetadataConsistency should report if FCV upgrade have left legacy timeseries collections
-
- Backlog
-