[jira] [Assigned] (TS-1504) stats should not get a negative value

2012-11-10 Thread Bin Chen (JIRA)

 [ 
https://issues.apache.org/jira/browse/TS-1504?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Bin Chen reassigned TS-1504:


Assignee: taorui  (was: Bin Chen)

> stats should not get a negative value
> -
>
> Key: TS-1504
> URL: https://issues.apache.org/jira/browse/TS-1504
> Project: Traffic Server
>  Issue Type: Bug
>  Components: Stats
>Affects Versions: 3.3.0
>Reporter: Zhao Yongming
>Assignee: taorui
> Fix For: 3.3.2
>
>
> {code}
> proxy.process.http.transaction_totaltime.hit_fresh.process=-8090340352.00
> proxy.process.cluster.open_delays=-1568985805836593376
> proxy.process.cluster.connections_avg_time=-76.100204
> proxy.process.cluster.control_messages_avg_send_time=-92.242027
> proxy.process.cluster.open_delay_time=-1147.221313
> proxy.process.cluster.rmt_cache_callback_time=-214.001053
> proxy.process.cluster.remote_connection_time=-259.256744
> {code}

--
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


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

2012-11-10 Thread Bin Chen (JIRA)

[ 
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


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

2012-11-10 Thread Bin Chen (JIRA)

[ 
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