Serialize InitializePlacementHistoryCoordinator with the execution of DDL operations & Topology changes

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Fixed
    • Priority: Major - P3
    • 8.3.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Catalog and Routing
    • Fully Compatible
    • CAR Team 2025-08-18, CAR Team 2025-09-01, CAR Team 2025-09-15, CAR Team 2025-09-29, CAR Team 2025-10-13
    • 🟥 DDL
    • None
    • None
    • None
    • None
    • None
    • None

      Today, the initialization of config.placementHistory is implemented through a ShardingCatalogManager method that provides limited resilience to step down events of the config server and ability to serialize with incompatible operations - namely:

      1. targeting queries from change stream readers
      2. commit of DDL operations & chunk migrations
      3. topology changes
      4. removal of disposable documents of config.placementHistory.

      The InitializePlacementHistoryCoordinator introduced with SERVER-108943 is meant to close the gap.

      The objective of this ticket is to modify the coordinator to ensure proper serialization between the execution of the new coordinator VS:

      • Sharding DDL commands being executed cluster-wide
      • addShard  / removeShardCommit.

            Assignee:
            Paolo Polato
            Reporter:
            Paolo Polato
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: