On May 19, 7:25 pm, "Parama W. Danoesubroto" <[email protected]> wrote: > How about if I have a long running job, and then I deployed new changes?
I asked Heroku this same question because I was also curious. Their response was: on deploys workers are killed using the same method I just mentioned [SIGTERM followed by a SIGKILL a few second later] and new workers are started So if you have a running task on deploy it could get stuck until the max_run_time timeout. I guess if you were really concerned about this you could add some sort of database flag to DelayedJob to tell DelayedJob to stop running jobs. Wait all currently running jobs are finished then deploy. -- 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.
