checkMetadataConsistency should indicate which shards have divergent index properties

XMLWordPrintableJSON

    • Catalog and Routing
    • CAR Team To Be Assigned
    • 2
    • None
    • 3
    • TBD
    • 🟥 DDL
    • None
    • None
    • None
    • None
    • None
    • None

      Currently, when checkMetadataConsistency is run with the checkIndexes parameter and encounters an inconsistency, it produces the following output:

            {
        type: 'InconsistentIndex',
        description: 'Found an index of a sharded collection that is inconsistent between different shards',
        details: {
          namespace: 'test.coll',
          info: {
            missingFromShards: [],
            inconsistentProperties: [
              { k: 'expireAfterSeconds', v: Long('600') },
              { k: 'expireAfterSeconds', v: 3600 }
            ],
            indexName: 'indx_1'
          }
        }
      }

      However, this output lacks information about which shards are associated with the inconsistent index properties. To improve debuggability, the output should explicitly indicate which shard has which index configuration.

              Assignee:
              Unassigned
              Reporter:
              Pol Pinol
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated: