Inconsistency Types

A collection contains mismatching options across different shards.

A collection exists on a shard with a locally registered UUID that differs from the one registered in the config.collections cluster catalog.

The routing table contains a chunk with a min key or max key that doesn't correspond to the collection shard key.

The routing table contains a zone with a min key or max key that doesn't correspond to the collection shard key.

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

An index exists on two different shards that contains differing metadata or a specific index is missing on some shards.

Indicates that an unsharded collection exists on the incorrect shard and was not moved with moveCollection.

A collection is registered on the sharding catalog but does not exist on the corresponding shard.

A sharded collection exists without a routing table.

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

A range gap exists in the routing table. The last chunk boundary in the routing table does not reach the maximum key value.

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

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

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

A shard is missing routing information for a collection.

A shard thinks a sharded collection is unsharded.

An unsharded collection has an invalid shard key.

An unsharded collection contains multiple chunks.

Overlapping zones exist for the same collection.