Verify no authoritative DDL coordinator hits the unbarriered config-read-then-shard-write pattern

XMLWordPrintableJSON

    • Catalog and Routing
    • Fully Compatible
    • CAR Team 2026-06-22, CAR Team 2026-07-06
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Double-check whether any authoritative DDL coordinator matches all three of the following:

      • (1) writes to the config server, then reads back what it wrote, then writes to the shard local catalog
      • (2) does so across different phases
      • (3) lacks a barrier (linearizable read) before that sequence.

      Coordinators meeting all three conditions are prone to data corruption even in the authoritative model.

            Assignee:
            Pol Pinol
            Reporter:
            Pol Pinol
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: