#What do the job statuses mean in practice?

1 messages · Page 1 of 1 (latest)

kindred plank
#

Could someone please explain what the various job status mean in practice? E.g. pending, queued, delayed?

What is delayed digest job?
What is a pending digest job?
What is a pending in-app job? Sent but unread?
What is a pending trigger?

Is there any documentation I could read about this?

rapid shoal
#

<@&943775970421264404> could you please help us here?

dawn plume
kindred plank
#

Thanks @dawn plume. So if I have a lot of pending jobs, how can I speed this up? Adding more workers?

dawn plume
glossy orchidBOT
kindred plank
#

@dawn plume no matter how much resource I put into it, I just end up with tons of pending jobs. I get why if I'm triggering faster than I can process I build up a backlog, but it's running into millions of pending jobs and a tiny few actually get delivered. I've got like millions of in-app pending tasks.

It seems like the trouble is topics with lots of subscribers and a 1 day digest just spends all its time digesting and not delivering

#

Is there a way to run workers that just look for certain statuses? E.g. have a worker processing triggers and one processing pending jobs?

kindred plank
#

For posterity: ended up deleting a bunch of old jobs that were stuck. Since upgrading to 0.21, haven't yet seen the same problem

dawn plume
#

I am not sure why that way happening. The way the worker works is that they round robin over every topic which is inefficient, this is most likely way it seemed like it was not helping.