nathanl
Jobs stuck as available in a partitioned queue
I’ve got some jobs that are “stuck”. Eg, one is scheduled 20 hours ago and is in available on attempt 0 of 15. It’s part of a workflow and has deps, but searching meta.workflow_id:0198ec97-ad63-783d-9c6b-12f1c6a15728 in all states finds only this stuck job in available.
The queue has config global_limit: [allowed: 1, partition: [fields: [:args], keys: [:regression_model_id]]], local_limit: 5. Yesterday I got some of these jobs to run by temporarily bumping that to 2, but that’s not very safe. This is on oban_pro 1.6.3, oban 2.20.1, oban_met 1.0.3, oban_web 2.11.4. For config we’ve got notifier: Oban.Notifiers.PG.
Any suggestions to debug?
Most Liked
sorentwo
The Oban version looks good, but a fix in Pro v1.6.4 may help with the stuck processing.
The fact that there’s a job in a workflow with deps that is marked available means all the deps have already completed (or cancelled/discarded depending on your config).







