[jira] [Commented] (TS-4187) connections_currently_open stat not accurate with global server session pools

["ASF GitHub Bot (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/TS-4187?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15269708#comment-15269708 ] 

ASF GitHub Bot commented on TS-4187:
------------------------------------

Github user shinrich commented on the pull request:

    https://github.com/apache/trafficserver/pull/583#issuecomment-216679006
  
    I think you could do a TSQA test.  Configure with global pools.   Run a set of requests through.  Wait a while for things to drain out.  Verify that the current_open connection count is 0 or really close to 0.  I don't see how to do an integration test that would exercise this case.  


> connections_currently_open stat not accurate with global server session pools
> -----------------------------------------------------------------------------
>
>                 Key: TS-4187
>                 URL: https://issues.apache.org/jira/browse/TS-4187
>             Project: Traffic Server
>          Issue Type: Bug
>            Reporter: Susan Hinrichs
>            Assignee: Susan Hinrichs
>             Fix For: 6.2.0
>
>
> When global server session pools are used, sockets may be moved to new VCs associated with different threads.  The connections_currently_open stat was not being correctly incremented in that case meaning the connections_currently_open stat would go negative.
> This means that the connection throttling logic would likely not trigger. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)