[SERVER-46084] Don't use $setUnion in aggregation for finding inconsistent sharded indexes Created: 11/Feb/20  Updated: 29/Oct/23  Resolved: 24/Mar/20

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: None
Fix Version/s: 4.2.6, 4.4.0-rc0, 4.7.0

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

Issue Links:
Backports
Documented
is documented by DOCS-13540 Investigate changes in SERVER-46084: ... Closed
Duplicate
is duplicated by SERVER-46483 Verify inconsistent sharded indexes p... Closed
Gantt Dependency
Related
is related to SERVER-44916 Test and document a pipeline to find ... Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Backport Requested:
v4.4, v4.2
Sprint: Sharding 2020-02-24, Sharding 2020-03-09, Sharding 2020-03-23, Sharding 2020-04-06
Participants:

 Description   

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.



 Comments   
Comment by Githook User [ 30/Mar/20 ]

Author:

{'name': 'Jack Mulrow', 'email': 'jack.mulrow@mongodb.com', 'username': 'jsmulrow'}

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

(cherry picked from commit 2eaf0ba58cca9e96276e8a07a3d46f0a7b83289d)
Branch: v4.4
https://github.com/mongodb/mongo/commit/57d5c7e6cee04491102b7b104e4a0f9531cb18f0

Comment by Githook User [ 27/Mar/20 ]

Author:

{'name': 'Cheahuychou Mao', 'username': 'cheahuychou', 'email': 'cheahuychou.mao@mongodb.com'}

Message: SERVER-45389 Add metrics tracking how often shards have inconsistent indexes

(cherry picked from commit ea696eb7a27f18c21223a3ff94d9124f06698af5)

SERVER-46084 Don't use setUnion in aggregation for finding inconsistent sharded indexes

(cherry picked from commit 2eaf0ba58cca9e96276e8a07a3d46f0a7b83289d)
Branch: v4.2
https://github.com/mongodb/mongo/commit/decfd07f05e7d9a65cfd07e42c07456f5a72b6f4

Comment by Githook User [ 24/Mar/20 ]

Author:

{'name': 'Jack Mulrow', 'username': 'jsmulrow', 'email': 'jack.mulrow@mongodb.com'}

Message: SERVER-46084 Don't use setUnion in aggregation for finding inconsistent sharded indexes
Branch: master
https://github.com/mongodb/mongo/commit/2eaf0ba58cca9e96276e8a07a3d46f0a7b83289d

Comment by Jack Mulrow [ 27/Feb/20 ]

David Storch, thanks for the update. I already had this ticket mostly done though, so I figure I may as well just knock it out now so we don't have to worry about the timeline for SERVER-29425.

Comment by David Storch [ 26/Feb/20 ]

jack.mulrow, as a heads up pawel.terlecki is currently working on SERVER-29425. I'm not sure if he knows exactly when it will land, but I wanted to let you know in case that affects your plan for this ticket.

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