Task processor queue overload

Hi there!

I’ve read in several places that warnings about the task processor queue reaching its limit are an indication of an overloaded server. However, I see these warnings also on servers with relatively little load, which have many queues configured.

I can easily reproduce this on my test server, which has about 40 SIP peers, and 2000 queues defined in queues.conf. On an otherwise idle system, if I change queues.conf, and issue a queue reload all command on the CLI, I get several messages like:

WARNING[10346]: taskprocessor.c:913 taskprocessor_push: The ‘subm:ast_device_state_topic-00000002’ task processor queue reached 500 scheduled tasks again.

To be honest, this worries me a bit. On live servers we see a similar behaviour when calls are coming in (it looks like when you have many queues, even a single call triggers the taskprocessor warning).

Since these servers are otherwise idle, and don’t process much traffic, I’m not inclined to look at adding hardware. So, is there something else I could look at?

This is with Debian Buster, asterisk 1:16.2.1~dfsg-1+deb10u1

Thanks for any tips! Best regards, Roel

1 Like

I have the same problem with “task processor queue reached 500 scheduled tasks again”

Why do you believe it is the same problem, given that the original poster’s underlying problem doesn’t seem to have been diagnosed, so we don’t know what the problem was!

because I get that error on my asterisk cli, I can send you information you need to find the problem,
or I post a new topic if you say

It’s a warning, not an error, and it is a symptom of many underlying problems. You need to work out what your system is doing that is unusual. You also need to work out what is not working, or is working too slowly, as that is the problem you should really be addressing.

You should start a new topic if the only thing in common is the task processor queue length warning.

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.