-
Notifications
You must be signed in to change notification settings - Fork 588
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[4.x] Fixes jobs saying "pending" forever #1349
Conversation
… into fix/pending-job-status
@nunomaduro is it normal to see a lot of this queue jobs from this class ? |
@malohtie Yes, I am assuming you have an even bigger number of 'other' queued jobs, right? |
@nunomaduro yes a lot |
So that number of "ProcessPendingUpdates" is expected, as some of your queued job jobs are being finished before even you insert them in telescope. |
I'm seeing these jobs dispatched to the default queue too. What does it do ? In what case is it dispatched ? I can't find any documentation about it. |
FYI this is a very noisy job so it is a good candidate for silencing in the |
Hi and thanks for your reply but I don't use Horizon. To me the problem is that an undocumented job is dispatched on an unconfigurable queue, to do I don't know what or when. I'm not sure how should I handle it at this time and why should I handle it. |
I agree with you, I think this could be handled better. Was just offering a temporary solution while using Horizon to remove the many jobs from the completed list there. |
Could this PR be a possible solution to this problem on the horizon? |
This is making millions of jobs for me, my default queue has gone from 2 threads to 30, just to keep up. all jobs have specific queues in Horizon and so this is all to handle this patch. I can ignore them from the completed queue in horizon but it will still be running 30 threads just for this job. If you update the config (config/telescope.php) to set this as false, it will stop the job running and you can use Horizon for monitoring the jobs |
This pull request fixes the "pending" job status (#1331, #1113, #577, #507, #543, #690, #503, #411), by simply delaying the "failed" updates to performed a few seconds after via queued job.