[SERVER-73028] Investigate need of new index for auto-merging Created: 19/Jan/23  Updated: 29/Oct/23  Resolved: 07/Mar/23

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 7.0.0-rc0

Type: Task Priority: Major - P3
Reporter: Pierlauro Sciarelli Assignee: Pierlauro Sciarelli
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Assigned Teams:
Sharding EMEA
Backwards Compatibility: Fully Compatible
Sprint: Sharding EMEA 2023-02-06, Sharding EMEA 2023-02-20, Sharding EMEA 2023-03-06
Participants:

 Description   

The code committed SERVER-72283 is performing a query on config.chunks extracting chunks on fields <uuid, shard, forceJumbo, onCurrentShardSince> and ordering the result by min.

Aim of this ticket is to investigate whether to:

  • Simply keep the existing index on <uuid, shard, min>
    OR
  • Remove the index existing index and create a new one with more fields: <uuid, shard, min, onCurrentShardSince, jumbo>

Additionally, a new index will be added for the initial query performed by the auto-merger to identify <shards, nss> tuples for which it is possible to issue auto-merge requests.



 Comments   
Comment by Githook User [ 07/Mar/23 ]

Author:

{'name': 'Pierlauro Sciarelli', 'email': 'pierlauro.sciarelli@mongodb.com', 'username': 'pierlauro'}

Message: SERVER-73028 Add index supporting automerger query on `config.chunks`
Branch: master
https://github.com/mongodb/mongo/commit/7208ec2715d1726451d9aaf730d2bc9b3969e15d

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