-
Type:
Improvement
-
Resolution: Unresolved
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
Catalog and Routing
-
CAR Team 2025-11-24, CAR Team 2025-12-08
-
2
-
🟥 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.