Add ShardRole assertions to check routers attach placementConflictTime when routing transactions

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Catalog and Routing
    • CAR Team 2025-03-17, CAR Team 2025-03-31, CAR Team 2025-04-14, CAR Team 2025-04-28, CAR Team 2025-05-12, CAR Team 2025-05-26, CAR Team 2025-06-09
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      The protocol for multi-document transactions on sharded clusters with

      readConcern = {local|majority} 

      is such that requires routers to attach a placementConflictTime to the shard requests. Failure to do so could lead to correctness anomalies when transactions execute concurrenctly with DDL. This ticket is to consider adding checks on the ShardRole acquisitions to ensure that this protocol is being followed.

            Assignee:
            Enrico Golfieri
            Reporter:
            Jordi Serra Torrens
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: