Inconsistency Types

New in version 7.0. :

The checkMetadataConsistency command performs a series of consistency checks on sharding metadata and indexes and returns an array of inconsistency documents.

Inconsistency Type	Description
`CollectionAuxiliaryMetadataMismatch`	A collection contains mismatching auxiliary metadata across different shards. New in version 8.1. :
`CollectionOptionsMismatch`	A collection contains mismatching options across different shards. New in version 8.0(Also available starting in 7.0.23). :
`CollectionUUIDMismatch`	A collection exists on a shard with a locally registered UUID that differs from the one registered in the `config.collections` cluster catalog. New in version 7.0. :
`CorruptedChunkShardKey`	The routing table contains a chunk with a min key or max key that doesn't correspond to the collection shard key. New in version 7.0. :
`CorruptedZoneShardKey`	The routing table contains a zone with a min key or max key that doesn't correspond to the collection shard key. New in version 7.0. :
`HiddenShardedCollection`	A collection is registered in the `config.collections` cluster catalog under a non-existent database. New in version 7.0. :
`InconsistentIndex`	An index exists on two different shards that contains differing metadata or a specific index is missing on some shards. New in version 7.0. :
`MisplacedCollection`	Indicates that an unsharded collection exists on the incorrect shard and was not moved with `moveCollection`. New in version 7.0. : Changed in version 8.0. :
`MissingLocalCollection`	A collection is registered on the sharding catalog but does not exist on the corresponding shard. New in version 8.0. :
`MissingRoutingTable`	A sharded collection exists without a routing table. New in version 7.0. :
`MissingShardKeyIndex`	A sharded collection exists that doesn't have an index compatible with the collection shard key. New in version 7.0. :
`RangeDeletionMissingShardKeyIndex`	A sharded collection exists that doesn't have an index compatible with the collection shard key and there is at least one remaining range deletion task to complete. New in version 8.2. :
`RoutingTableMissingMaxKey`	A range gap exists in the routing table. The last chunk boundary in the routing table does not reach the maximum key value. New in version 7.0. :
`RoutingTableMissingMinKey`	A range gap exists in the routing table. The first chunk does not start from the minimum key value. New in version 7.0. :
`RoutingTableRangeGap`	A range gap exists in the routing table between two consecutive chunks for the same collection. New in version 7.0. :
`RoutingTableRangeOverlap`	The routing table of a collection contains two chunks with overlapping shard key ranges. New in version 7.0. :
`ShardCatalogCacheCollectionMetadataMismatch`	A shard is missing metadata or routing information for a collection. New in version 8.2. :
`TrackedUnshardedCollectionHasInvalidKey`	An unsharded collection has an invalid shard key. New in version 8.0. :
`TrackedUnshardedCollectionHasMultipleChunks`	An unsharded collection contains multiple chunks. New in version 8.0. :
`ZonesRangeOverlap`	Overlapping zones exist for the same collection. New in version 7.0. :

Back

Stop

AuthoritativeShardCatalogCollectionsPresent