[SERVER-46483] Verify inconsistent sharded indexes pipeline output in mixed version clusters Created: 28/Feb/20  Updated: 24/Mar/20  Resolved: 24/Mar/20

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Jack Mulrow Assignee: Jack Mulrow
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
duplicates SERVER-46084 Don't use $setUnion in aggregation fo... Closed
Operating System: ALL
Sprint: Sharding 2020-03-09, Sharding 2020-03-23, Sharding 2020-04-06
Participants:

 Description   

The pipeline we'll use internally to discover inconsistent indexes uses output from $indexStats only present in v4.2.4 and later, and will use an aggregation expression $sort added in v4.4. We should verify that when run in a cluster with shards at mixed binary versions the pipeline does not incorrectly report inconsistent indexes and possibly do work to make the pipeline work better in such clusters.



 Comments   
Comment by Jack Mulrow [ 24/Mar/20 ]

Mixed version testing was added by SERVER-46084, so closing this ticket as a duplicate.

Generated at Thu Feb 08 05:11:38 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.