Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-72895

Implement shardKey index check in checkConsistencyMetadata command

XMLWordPrintableJSON

    • Type: Icon: Task Task
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 7.0.0-rc0
    • 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:

      1. Missing the index that supports the shard key
      2. The only remaining index compatible with shard key is multikey (SERVER-67299)
      3. 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.

            Assignee:
            pol.pinol@mongodb.com Pol Pinol
            Reporter:
            tommaso.tocci@mongodb.com Tommaso Tocci
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: