[asterisk-bugs] [JIRA] (ASTERISK-30447) Stasis/p:channel:all reaching 500 tasks
Luke Escude (JIRA)
noreply at issues.asterisk.org
Wed Mar 1 11:18:03 CST 2023
[ https://issues.asterisk.org/jira/browse/ASTERISK-30447?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=261487#comment-261487 ]
Luke Escude commented on ASTERISK-30447:
----------------------------------------
Okay that helps - I have two possible culprits:
1. Webhooks - these particular customers have POST webhooks occuring throughout their channels, as we send real-time call events to their 3rd party API. Since the CURL functions are blocking, a 2-second timeout being reached could be backing up the channel.
2. AMI monitoring daemon - As AMI feeds events to the monitoring system, it's possible I should queue up the events in a queue, instead of submitting them to our redis cluster in real-time, so it can free up the AMI socket more quickly.
Let me know if my logic doesn't make sense, and also I will look at upgrading to the next LTS version - Thanks Joshua!
> Stasis/p:channel:all reaching 500 tasks
> ---------------------------------------
>
> Key: ASTERISK-30447
> URL: https://issues.asterisk.org/jira/browse/ASTERISK-30447
> Project: Asterisk
> Issue Type: Bug
> Security Level: None
> Components: Applications/app_stasis
> Affects Versions: 16.30.0
> Reporter: Luke Escude
> Assignee: Luke Escude
>
> Starting last week, some of our larger Asterisk instaces are logging a bunch of these:
> The 'stasis/p:channel:all-0000513d' task processor queue reached 500 scheduled tasks.
> I haven't found much about the p:channel:all task processor (there's some documentation around the others, but not this one).
--
This message was sent by Atlassian JIRA
(v6.2#6252)
More information about the asterisk-bugs
mailing list