Loading...

XML

Word

Printable

JSON

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

Assigned Teams:

Catalog and Routing
Operating System:
ALL
CAR Domain/s:

🟦 Shard Catalog

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

The checkMetadataConsistency shard-key index check was disabled on secondaries in ~~SERVER-130595~~.

The check could report false positives on secondaries because it did not read the indexes and the CSR at a consistent point in time. Specifically, secondaries pin a snapshot timestamp for disk reads, but the CSR was not read using that same timestamp.

depends on

SERVER-130595 MoveRangeCoordinator should use the incremental authoritative commit

Closed

is related to

SERVER-130787 checkMetadataConsistency on secondary can report false positive due to CSR being newer than durable read timestamp

In Progress

SERVER-130595 MoveRangeCoordinator should use the incremental authoritative commit

Closed

Assignee:: Unassigned
Reporter:: Silvia Surroca
Participants:: Silvia Surroca
Votes:: 0 Vote for this issue
Watchers:: 1 Start watching this issue

Created:: Jul 08 2026 07:06:31 AM UTC
Updated:: Jul 09 2026 07:12:57 AM UTC

Details

Description

Attachments

Issue Links

Activity

People

Dates