Auto-merger must keep on issuing requests as long as there are mergeable chunks

XMLWordPrintableJSON

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

      Currently the auto-merger is issuing only one action per <shard,nss> by popping the collection from the map right after creating an action.

      Since SERVER-74405 introduced a limit of 1000 chunks to merge when serving requests issued by the auto-merger, the policy must keep on returning actions as long as there are chunks to merge.

              Assignee:
              Pierlauro Sciarelli
              Reporter:
              Pierlauro Sciarelli
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: