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

Take into account mergeability constraints in` mergeAllChunksOnShard`

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

      SERVER-71612 introduced a catalog manager method merging in one-shot contiguous sequences of chunks for a given collection for a given shard.

      Purpose of this ticket is to enhance that method in order to take into account the onCurrentShardSince field introduced by SERVER-71615 and the jumbo flag.

      Two or more contiguous non-jumbo chunks belonging to the same collection are going to be considered mergeable when they are owned by the same shard and their history can be safely purged without breaking transactions and snapshot reads.

      Technically, this means that each chunk to merge is required to fulfill the following conditions:

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

              Created:
              Updated:
              Resolved: