-
Type:
Task
-
Resolution: Gone away
-
Priority:
Major - P3
-
None
-
Affects Version/s: 7.0.0, 8.0.0, 9.0.0-rc0, 8.3.0
-
Component/s: None
-
None
-
Catalog and Routing
-
CAR Team 2026-08-31, CAR Team 2026-09-14
-
135
-
🟥 DDL
-
None
-
None
-
None
-
None
-
None
-
None
The background metadata consistency check can fail when its catalog snapshot expires before the aggregation cursor is established, returning SnapshotTooOld error. Although minSnapshotHistoryWindowInSeconds defaults to 300s, config-fuzzer suites can run with a much shorter snapshot-history window.
As part of this ticket, we need to update the metadata consistency hook to abort the current check and retry the full check later with a fresh snapshot timestamp instead of failing the test. This can be achieved by setting the the SnapshotTooOld error as transient in the CMC isTransientError() function.
- is related to
-
SERVER-70759 Fuzz sharding parameters in config fuzzer
-
- Closed
-
- related to
-
SERVER-132175 checkMetadataConsistency may return SnapshotUnavailable from failed internal snapshot read
-
- Closed
-
-
-
- Backlog
-