[
https://issues.apache.org/jira/browse/TS-1815?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Phil Sorber resolved TS-1815.
-----------------------------
Resolution: Not A Problem
Fix Version/s: (was: 5.0.0)
4.2.0
While this wasn't a real bug, I did add some code to make it clear what all the
accept threads were for. There is now a thread number and a port.
{noformat}
10336 nobody 20 0 659m 122m 4688 S 0.0 0.1 0:00.00 [ACCEPT 0:80]
10340 nobody 20 0 659m 122m 4688 S 0.0 0.1 0:00.00 [ACCEPT 0:8084]
{noformat}
> N+1 ACCEPT threads?
> -------------------
>
> Key: TS-1815
> URL: https://issues.apache.org/jira/browse/TS-1815
> Project: Traffic Server
> Issue Type: Bug
> Components: Network
> Reporter: Zhao Yongming
> Fix For: 4.2.0
>
>
> well, just noted that we have N+1 accept threads, but we have only N threads
> in use, what is the problem here?
> {code}
> [root@test67 trafficserver]# top -b -n 1 -H -M -S | grep ACCEPT
> 15800 ats 20 0 18.1g 10g 4720 R 18.5 23.4 217:15.38 [ACCEPT]
> 15801 ats 20 0 18.1g 10g 4720 S 18.5 23.4 216:49.99 [ACCEPT]
> 15802 ats 20 0 18.1g 10g 4720 S 18.5 23.4 216:49.44 [ACCEPT]
> 15799 ats 20 0 18.1g 10g 4720 S 16.6 23.4 218:04.94 [ACCEPT]
> 15805 ats 20 0 18.1g 10g 4720 S 0.0 23.4 0:00.36 [ACCEPT]
> [root@test67 trafficserver]# grep ACCEPT
> /opt/ats/etc/trafficserver/records.config -i
> CONFIG proxy.config.accept_threads INT 4
> {code}
--
This message was sent by Atlassian JIRA
(v6.1#6144)
