Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-73028

Investigate need of new index for auto-merging

    • Type: Icon: Task Task
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 7.0.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Sharding EMEA
    • Fully Compatible
    • Sharding EMEA 2023-02-06, Sharding EMEA 2023-02-20, Sharding EMEA 2023-03-06

      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.

            Assignee:
            pierlauro.sciarelli@mongodb.com Pierlauro Sciarelli
            Reporter:
            pierlauro.sciarelli@mongodb.com Pierlauro Sciarelli
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: