You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@mperham explained to me that you could not kill a thread in a worker process as it is quite dangerous. However for my usecase, I need total control on job killing. I am thinking of running multiple workers each with 1 thread, so I could kill the PID instead. It does come with a resource cost though. And then @mperham suggested this: "or have the worker thread check if should it halt". I don't truly understand what does it mean, this ticket is dedicated for explanation on that
The text was updated successfully, but these errors were encountered:
Can you explain the job your worker is performing? At a high level, I'm speaking something like this:
defperformwhileactive? && !donedo_somethingendend
The active? check could verify the job has not been cancelled. That's the point of the JID: it's a global identifier you can use to power this type of thing.
@mperham I think you misunderstand me. In my use case, some job takes too long and I could not figure out how to kill a single job (which is probably running in a thread)
@mperham explained to me that you could not kill a thread in a worker process as it is quite dangerous. However for my usecase, I need total control on job killing. I am thinking of running multiple workers each with 1 thread, so I could kill the PID instead. It does come with a resource cost though. And then @mperham suggested this: "or have the worker thread check if should it halt". I don't truly understand what does it mean, this ticket is dedicated for explanation on that
The text was updated successfully, but these errors were encountered: