Remove dedicated executor for moveChunk/moveRange commands

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major - P3
    • 7.0.0-rc0, 6.0.6, 6.3.1
    • Affects Version/s: None
    • Component/s: None
    • None
    • Sharding EMEA
    • Fully Compatible
    • ALL
    • v6.3, v6.0, v5.0, v4.4
    • Sharding EMEA 2023-04-17
    • 135
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      SERVER-45338 added a dedicated mono-threaded executor to be used for moveChunk commands (then moved to manage moveRange commands starting from v6.0) but there seems to be no reason to keep on using a separate executor rather than picking a thread from the fixed executor.

      The reason behind this comment seems to be that the idea was having a one-threaded executor to guarantee that only one migration at a time could run, however the same guarantee is already provided by the ActiveMigrationsRegistry.

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

              Created:
              Updated:
              Resolved: