Hi Richard,
I've just had another task processor max out, this time with the following
thread:
pjsip/distributor-000000c7 1286 513 10
450 500
All other threads around this are processing very few tasks:
pjsip/distributor-000000b1 1745 0 4
450 500
pjsip/distributor-000000b2 1394 0 3
450 500
pjsip/distributor-000000b3 1408 0 3
450 500
pjsip/distributor-000000b4 1765 0 6
450 500
pjsip/distributor-000000b5 1600 0 3
450 500
pjsip/distributor-000000b6 1683 0 6
450 500
pjsip/distributor-000000b7 1421 0 4
450 500
pjsip/distributor-000000b8 1664 0 4
450 500
pjsip/distributor-000000b9 1514 0 4
450 500
pjsip/distributor-000000ba 2067 0 4
450 500
pjsip/distributor-000000bb 1477 0 4
450 500
pjsip/distributor-000000bc 1740 0 3
450 500
pjsip/distributor-000000bd 1468 0 4
450 500
pjsip/distributor-000000be 1313 0 3
450 500
pjsip/distributor-000000bf 1862 0 6
450 500
pjsip/distributor-000000c0 1592 0 4
450 500
pjsip/distributor-000000c1 1637 0 4
450 500
pjsip/distributor-000000c2 1613 0 4
450 500
pjsip/distributor-000000c3 2130 0 6
450 500
pjsip/distributor-000000c4 1825 0 8
450 500
pjsip/distributor-000000c5 1871 0 4
450 500
pjsip/distributor-000000c6 1508 0 4
450 500
pjsip/distributor-000000c7 1286 513 10
450 500
pjsip/distributor-000000c8 1892 0 5
450 500
pjsip/distributor-000000c9 1661 0 3
450 500
pjsip/distributor-000000ca 1771 0 5
450 500
pjsip/distributor-000000cb 1433 0 4
450 500
pjsip/distributor-000000cc 1644 0 6
450 500
pjsip/distributor-000000cd 1567 0 4
450 500
pjsip/distributor-000000ce 1738 0 3
450 500
pjsip/distributor-000000cf 1736 0 3
450 500
Shouldn't any task be distributed evenly across the above threads?
Kind regards,
Ross
________________________________
From: [email protected]
<[email protected]> on behalf of Richard Mudgett
<[email protected]>
Sent: 28 June 2016 17:00
To: Asterisk Developers Mailing List
Subject: Re: [asterisk-dev] ASTERISK-26145 - Task Process Issues possibly
caused by HEP
On Tue, Jun 28, 2016 at 10:20 AM, Ross Beer
<[email protected]<mailto:[email protected]>> wrote:
Hi,
I agree that the conversation about HEP default settings doesn't warrant a
lengthy discussion, however, the fact that the 'task processor' causes asterisk
to stop processing packets is a serious issue. This is happening multiple times
a day on several boxes.
I'm trying to identify what is causing over 1500 tasks to back-up in the
'subm:rtp_topic-000000de' scheduler. This is proving difficult as you only see
counts and not actual waiting tasks.
The res_hep_rtcp.so module is what creates the subm:rtp_topic stasis message
bus subscription. Since you have indicated that you are not using that feature
you should not load the module.
The taskprocessors that begin with 'subm:' (m for mailbox) or 'subp:' (p for
thread pool) are stasis message bus subscriptions. The 'subm:' taskprocessors
have a single dedicated thread to process the taskprocessor tasks. The 'subp:'
taskprocessors do not have a dedicated thread. Those taskprocessors get
executed by an available thread from the stasis thread pool. The stasis thread
pool is configured by the stasis.conf file.
Richard
--
_____________________________________________________________________
-- Bandwidth and Colocation Provided by http://www.api-digital.com --
asterisk-dev mailing list
To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-dev
