StaleConfig is currently being handled it 2 different places

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • Catalog and Routing
    • 1
    • 🟩 Routing and Topology
    • None
    • None
    • None
    • None
    • None
    • None

      We currently have duplicated stale-routing handling logic, in router_role.cpp, and in routing_context.cpp.

      The one from the routing context is only used from write_batch_response_processor.cpp.

      The goal of this ticket is to refactor and unify the entire stale exception handling in one place.

            Assignee:
            Unassigned
            Reporter:
            Meryama Nadim
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated: