-
-
Notifications
You must be signed in to change notification settings - Fork 1k
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
Pause, Resume, Kill/Cancel a Running Job #2650
Comments
Agreed, the inability to kill a running job can be a pain. especially when they occasionally get into a false "running" state and there's no easy way to evict it from the queue.
This sounds like it might be rather complex to get right, since once the |
I need to know more about the events within the underlying job queue system, specifically how do you pass along percentage updates? I might be wrong here but it doesn't look like we assign a unique ID to each job, so there's currently no way to modify it once it's been kicked off, right? I think this is how I might tackle this specific improvement:
|
Related: |
Relates to #1127, relates to #2650. This commit adds a mechanism to track cancellation of jobs in Redis using pub/sub on a custom set which tracks the IDs which have been cancelled. The job process functions will still continue to execute unless there is specific logic to check the job state and throw an error on cancellation.
Is your feature request related to a problem? Please describe.
I would like the ability to pause, resume, and kill/cancel a job that is currently running and events that we can listen for our own custom jobs.
Describe the solution you'd like
Currently when I try to cancel a running job, like a full re-index which takes a very long time, it gives me an error saying I can't stop a job while it's running. I would like the ability to pause a job and then resume it, or cancel it altogether.
Describe alternatives you've considered
I'm not sure what alternatives there would be.
The text was updated successfully, but these errors were encountered: