Update "connections" server status section for maxEstablishing

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Fixed
    • Priority: Major - P3
    • 8.2.0-rc0, 8.1.2
    • Affects Version/s: None
    • Component/s: None
    • None
    • Networking & Observability
    • Fully Compatible
    • v8.1, v8.0, v7.0
    • N&O 2025-05-12, N&O 2025-05-26
    • 0
    • None
    • 3
    • TBD
    • None
    • None
    • None
    • None
    • None
    • None

      Update the "connections" server status section to ensure that the following is true:

      • connections.queued will be added to reflect all connections that are queued waiting for establishment.
      • connections.current will reflect all established connections, regardless of whether or not they are being used to run an operation.
      • connections.active will reflect all connections being actively used to run an operation.
      • connections.available will be equal to maxIncomingConnections - (connections.queued + connections.current)
      • connections.created will be modified to be incremented after the establishment token has been acquired
      • connections.rejected will be unchanged and will still reflect connections rejected due to the maxIncomingConnections limit.
      • connections.establishmentRateLimit.totalRejectedConnections will be added reflect connections rejected due to exceeding MaxQueueDepth.
      • connections.establishmentRateLimit.totalExemptedFromEstablishmentRateLimiting will be added to track how many connections were exempted from establishment rate limiting.
      • connections.establishmentRateLimit.totalInteruptedDueToClientDisconnect will be added to reflect connections that left the queue due to client disconnect

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

              Created:
              Updated:
              Resolved: