Make DDLs operations resilient to add/remove shard

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Fixed
    • Priority: 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
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      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
              Reporter:
              Pierlauro Sciarelli
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: