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

Make DDLs operations resilient to add/remove shard

    • Type: Icon: Task Task
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 8.1.0-rc0, 8.0.0-rc6
    • Affects Version/s: None
    • Component/s: None
    • None
    • Catalog and Routing
    • Fully Compatible
    • v8.0
    • CAR Team 2024-05-27
    • 200

      Several DDL coordinators are executing operations on multiple shards by retrieving their list from the shard registry when needed, often assuming the set of shards to be stable during the whole duration of the DDL.
      As a consequence, when shards are added/removed while DDLs are ongoing may result in partially executing metadata changes on some shards (in the best cases) and potentially in causing coordinators to get stuck (in the worse cases).

      Purpose of this ticket is to provide a novel synchronization/serialization mechanism between DDLs and add/remove shard so that they can be executed concurrently with no side effects.

            Assignee:
            jordi.serra-torrens@mongodb.com Jordi Serra Torrens
            Reporter:
            pierlauro.sciarelli@mongodb.com Pierlauro Sciarelli
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: