-
Type:
Bug
-
Status: Closed
-
Priority:
Major - P3
-
Resolution: Fixed
-
Affects Version/s: None
-
Component/s: Sharding
-
Labels:None
-
Backwards Compatibility:Fully Compatible
-
Operating System:ALL
-
Backport Requested:v4.4, v4.2
-
Epic Link:
-
Sprint:Sharding 2020-02-24, Sharding 2020-03-09, Sharding 2020-03-23, Sharding 2020-04-06
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.
- is documented by
-
DOCS-13540 Investigate changes in SERVER-46084: Don't use $setUnion in aggregation for finding inconsistent sharded indexes
-
- Closed
-
- is duplicated by
-
SERVER-46483 Verify inconsistent sharded indexes pipeline output in mixed version clusters
-
- Closed
-
- is related to
-
SERVER-44916 Test and document a pipeline to find inconsistent indexes
-
- Closed
-