Assign each gRPC channel a unique id

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major - P3
    • 8.1.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • Networking & Observability
    • Fully Compatible
    • ALL
    • Egress gRPC 2025-02-14
    • 0
    • 1
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      The gRPC library will reuse existing connections, even if the stream has requested to use a different channel object, unless the new channel object has a unique id associated with it. This means that if any RPCs are alive when we drop channels, we will not actually drop the connections themselves and may reuse them in the future. There is a simple fix here, which is to assign gRPC channels unique ids.

            Assignee:
            Erin McNulty
            Reporter:
            Erin McNulty
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: