I forgot to add, this behaviour seems to occur when ramping up or down the amount of workers too. Setting workers to 2 and then back down to 1 leaves a locked job.
On Nov 17, 4:29 am, empika <[email protected]> wrote: > Hallo > > Ive noticed that when pushing code to Heroku, it kills (I think) the 1 > running worker I have and starts a new one without gracefully killing > the old one. The job that the worker was running on remains locked > while the new worker continues. I ended up with about 6 jobs that were > locked and needed restarting earlier, it wasn't till I noticed that > they we're not running and investigated that I figured out what was > happening. > > Any ideas on how to stop this happening? > > Thanks > Edd -- You received this message because you are subscribed to the Google Groups "Heroku" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/heroku?hl=en.
