[jira] [Commented] (TS-1492) if being net_connections_throttled, ts must to be restarted?(because of can't accept health checking request)

["Bin Chen (JIRA)" <ji...@apache.org>]

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

Bin Chen commented on TS-1492:
------------------------------

if we should restart traffic_server, set stat records=1. And if ts restored, then we must set stat records=0. But maybe have more case(throttling, cache error), one is setting, and other is restoring, how to set stat records? so maybe we can't use only one stat records.
                
> if being net_connections_throttled,  ts must to be restarted?(because of can't accept health checking request)
> --------------------------------------------------------------------------------------------------------------
>
>                 Key: TS-1492
>                 URL: https://issues.apache.org/jira/browse/TS-1492
>             Project: Traffic Server
>          Issue Type: Improvement
>          Components: Core
>    Affects Versions: 3.2.0
>            Reporter: Bin Chen
>            Assignee: Bin Chen
>            Priority: Critical
>             Fix For: 3.3.1
>
>         Attachments: backdoor_not_throttling.patch
>
>
> In our env, ts will be throttled because of many request incomming simultaneously(because of frontend haproxy is restarted). But we don't expect ts be restarted because of this case. we can handled this:
> 1、if throttled, ts's health check request always be handled
> 2、many many connection request may be handled in long time

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira