Only parent routers assert that additional participants have readOnly value on successful response

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Fixed
    • Priority: Major - P3
    • 8.0.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Cluster Scalability
    • Fully Compatible
    • Cluster Scalability 2024-2-19, Cluster Scalability 2024-3-4
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      In a certain case (TBD), participants in TransactionRouter exist with ReadOnly not set to a bool value. However this causes an improper invariant failure on p.second.readOnly != Participant::ReadOnly::kUnset in TransactionRouter::Router::getAdditionalParticipantsForResponse().

      Find and verify the code flow that properly adds participants with unset ReadOnly; remove the invariant. If the read-only state is known in this case, set it properly, or default it to true.

        1. git.diff
          7 kB

              Assignee:
              Janna Golden
              Reporter:
              Israel Hsu (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: