Problems with Delayed::Job on Heroku


#1

We can only deploy to Heroku now when there are no delayed_jobs running. The reason being that upon deployment, Heroku sends a SIGTERM which eventually results in a SIGKILL on the job. This creates problems where I have to clean up the docker containers manually and may even leave our data in a dirty state (being cut off when POSTing the results).

We’re current raising an exception whenever we get a SIGTERM but that is still bad.
https://github.com/collectiveidea/delayed_job/commit/90579c3047099b6a58595d4025ab0f4b7f0aa67a

Hopefully someone might have a better idea.


#2

Maybe we could also use a queuing system on linux itself. Delayed::Job would just be responsible for pinging the service.


#3

No longer deployed on heroku.