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

Compute missing bound of `moveRange` within MigrationSourceManager

    XMLWordPrintableJSON

Details

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Major - P3 Major - P3
    • 6.0.0-rc3, 6.1.0-rc0
    • None
    • None
    • None
    • Fully Compatible
    • v6.0
    • Sharding EMEA 2022-04-18, Sharding EMEA 2022-05-02

    Description

      When moveRange is only invoked with one bound, the missing bound is currently computed outside the MigrationSourceManager before running a refresh. Purpose of this ticket is to optimize the current logic by moving the bound calculation after the onShardVersionMismatch to be sure that the routing table is not stale.

      Attachments

        Activity

          People

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

            Dates

              Created:
              Updated:
              Resolved: