-
Type:
Bug
-
Resolution: Duplicate
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
Catalog and Routing
-
ALL
-
CAR Team 2026-07-20
-
None
-
None
-
None
-
None
-
None
-
None
-
None
internal_transactions_kill_sessions is throwing an inconsistency between shard catalog (durable and in-memory) vs global catalog.
[j1:s0:n1] | 2026-07-07T08:42:21.090+00:00 W SHARDING 7514800 [S] [conn32] "Detected sharding metadata inconsistency","attr":{"inconsistency":{"type":"InconsistentShardCatalogCollectionMetadata","description":"Found inconsistencies between collection metadata in the global catalog and the shard catalog","details":{"namespace":"test6_fsmdb0.fsmcoll0","collectionUUID":{"$uuid":"93f5d36d-252f-4162-a137-348320be4edd"},"details":{"field":"chunks","source":"inMemoryShardCatalog","mismatch":{"reason":"chunkCountMismatch","shardCatalogCount":1,"globalCatalogCount":2}}},"provenance":{"shardId":"shard-rs0_0","hostAndPort":"localhost:20354"}}}
- is duplicated by
-
SERVER-130787 checkMetadataConsistency on secondary can report false positive due to CSR being newer than durable read timestamp
-
- In Progress
-
- related to
-
SERVER-130787 checkMetadataConsistency on secondary can report false positive due to CSR being newer than durable read timestamp
-
- In Progress
-