connections.current gets temporarily incremented for sessions that would get rejected by the session establishment rate limiter

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Networking & Observability
    • ALL
    • N&O Prioritized List
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Upon accepting an ingress connection, we create a new SessionWorkflow object which increments the connection.current counter. Later, this session could be rate limited which would cause the counter to decrement. This temporary increment could be misleading since we don't actually have a connection that is waiting for data on the wire. We should consider updating this code such that we only increment connections.current after a session is accepted via the rate limiter.

            Assignee:
            Unassigned
            Reporter:
            Joseph Prince
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated: