[
https://issues.apache.org/jira/browse/TS-1492?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13494596#comment-13494596
]
Bin Chen commented on TS-1492:
------------------------------
the other solution, we can use one stat records to flagging one
case(throttling, cache not enable....), and traffic manager collect to
handler(check every case) traffic_server restart.
> 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
