Docs Menu

Docs HomeMongoDB Manual

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
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.

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.

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.

A collection is registered in the config.collections cluster catalog under a non-existent database.

New in version 7.0.

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.

Indicates that an unsharded collection exists on a shard that is not the primary shard.

New in version 7.0.

A sharded collection exists without a routing table.

New in version 7.0.

A sharded collection exists that doesn't have an index compatible with the collection shard key.

New in version 7.0.

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.

A range gap exists in the routing table. The first chunk does not start from the minimum key value.

New in version 7.0.

A range gap exists in the routing table between two consecutive chunks for the same collection.

New in version 7.0.

The routing table of a collection contains two chunks with overlapping shard key ranges.

New in version 7.0.

A shard thinks a sharded collection is unsharded.

New in version 7.0.

Overlapping zones exist for the same collection.

New in version 7.0.

←  Stop Defragmenting a Sharded CollectionCollectionUUIDMismatch →