Uploaded image for project: 'Documentation'
  1. Documentation
  2. DOCS-13540

Investigate changes in SERVER-46084: Don't use $setUnion in aggregation for finding inconsistent sharded indexes

    XMLWordPrintableJSON

Details

    Description

      Description

      Downstream Change Summary

      This ticket updated and finalized the aggregation pipeline we expect users to run to verify the indexes for a sharded collection are correct across all shards that was initially added by SERVER-44916. The pipeline is written out in full in this jstest: https://github.com/mongodb/mongo/blob/2eaf0ba58cca9e96276e8a07a3d46f0a7b83289d/jstests/sharding/index_stats_pipeline_detects_inconsistent_indexes.js#L20-L72

      Description of Linked Ticket

      The aggregation added in SERVER-44916 and used in SERVER-45389 to find inconsistent sharded indexes relies on $setUnion providing a consistent ordering, which is not supported. Instead, the pipeline will only consider fields known to be important, like name, key, and expireAfterSeconds untilĀ SERVER-29425 adds a supported way to sort an array.

      Scope of changes

      Impact to Other Docs

      MVP (Work and Date)

      Resources (Scope or Design Docs, Invision, etc.)

      Attachments

        Activity

          People

            kay.kim@mongodb.com Kay Kim (Inactive)
            backlog-server-pm Backlog - Core Eng Program Management Team
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:
              3 years, 42 weeks, 1 day ago