-
Type: Task
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: None
-
None
-
Sharding EMEA
-
Fully Compatible
-
Sharding EMEA 2023-01-23, Sharding EMEA 2023-02-06, Sharding EMEA 2023-02-20, Sharding EMEA 2023-03-06, Sharding EMEA 2023-03-20, Sharding EMEA 2023-04-03
As part of the goals of the project, we have to implement the checks for consistent indexes. These checks include:
- Missing the index that supports the shard key
- The only remaining index compatible with shard key is multikey (
SERVER-67299) Consistent indexes across shards:A sharded collection has an inconsistent index if the collection does not have the exact same indexes (including the index options) on each shard that contains chunks for the collection.Inconsistent indexes can occur, when a user is creating an index with a unique key constraint and one shard contains a chunk with duplicate documents.
- is related to
-
SERVER-74936 Improve shard key index inconsistency checks during migrations
- Closed
- related to
-
SERVER-75285 Deadlock between ShardsvrCheckMetadataConsistencyParticipantCommand, prepared transactions, and stepdown
- Closed
-
SERVER-74086 Implement checks for consistent indexes across shards
- Closed