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

Get rid of legacy `moveChunk` path once NOMAS milestone 1 is completed

    • 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-20, Sharding EMEA 2023-03-06, Sharding EMEA 2023-03-20, Sharding EMEA 2023-04-03

      Following the introduction of `moveRange` in v6.0, that review the move chunk paths to get rid of all the unused code.

      Examples:

      • Get rid of the moveChunk alias since only moveRange must be called by the CSRS in case of FCV >= v6.0 (keep in mind multiversion compatibility)
      • Get rid of _configsvrMoveChunk command as routers are calling into moveRange even if users invoke moveChunk (keep in mind multiversion compatibility)
      • Get rid of all requestMoveChunk calls in favour requestMoveRange and remove of all the dead code around (e.g. MoveChunkCommandInfo that will not be useful anymore)

            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: