-
Type:
Bug
-
Resolution: Fixed
-
Priority:
Major - P3
-
Affects Version/s: None
-
Component/s: Upgrade/Downgrade
-
None
-
Catalog and Routing
-
Fully Compatible
-
ALL
-
v8.3
-
CAR Team 2026-05-25
-
200
-
None
-
None
-
None
-
None
-
None
-
None
-
None
As part of the viewless timeseries project a new retriable error was introduced that gets returned if the targeted timeseries is undergoing an FCV upgrade/downgrade called InterruptedDueToTimeseriesUpgradeDowngrade.
This error is automatically handled in normal jstesting suites that use retriable writes. However, updateMany/deleteMany are not yet retriable. As such, it will propagate the error upwards and fail the error since it occurs outside of the runCommand method.
A search reveals that these jstests in the jstests/core/timeseries/write folder are susceptible to this failure:
- timeseries_delete_hint.js
- timeseries_delete_with_meta_concurrent.js
- timeseries_update_concurrent_arbitrary_updates_not_enabled.js
- timeseries_update_concurrent.js
- timeseries_update_hint.js
Out of those the timeseries_update* tests are already tagged requires_multi_updates. The timeseries_delete* tests also need this same tag as expected by the viewless timeseries FCV upgrade/downgrade excludes.
- is related to
-
SERVER-122589 Make timeseries passthrough tests using parallel shell & failpoints resilient to viewless timeseries upgrade/downgrade
-
- Closed
-