Loading...

XML

Word

Printable

JSON

Type: Task
Resolution: Unresolved
Priority: Major - P3
Fix Version/s: None
Affects Version/s: None
Component/s: None
Labels:
None

Assigned Teams:

Catalog and Routing
Story Points:
2
CAR Domain/s:

🟥 DDL

Aha! Reference:
None
Tracking Level:
None
Risk Status:
None
Exec Notes:
None
Goal Name(s):
None
Goal Link:
None

In CheckMetadataConsistency hook, we currently swallow malformed timeseries inconsistency found in stepdown suites .

With viewless timeseries collection SPM-3830 we can assume that no inconsistency can be generated even with stepdown suites, thus we should tighten the check performed by the CheckMetadataConsistency.

depends on

SERVER-119485 Add a persisted phase to setFCV after enabling target FCV features

Closed

is related to

SERVER-90889 Check timeseries collections throught the checkMetadataConsistency command

Closed

related to

SERVER-113967 Cleanup legacy timeseris code from CheckMetadataConsistency

Backlog

SERVER-113458 CheckMetadataConsistency should report if FCV upgrade have left legacy timeseries collections

Needs Scheduling

Assignee:: Unassigned
Reporter:: Tommaso Tocci
Participants:: Tommaso Tocci
Votes:: 0 Vote for this issue
Watchers:: 2 Start watching this issue

Created:: Nov 15 2025 06:24:24 AM UTC
Updated:: Jul 17 2026 10:21:31 AM UTC

Details

Description

Attachments

Issue Links

Activity

People

Dates

PagerDuty