Re:Show HN: goworker – a faster, Resque-compatible backgroun...
by jrallison on Monday September 16, 2013 @03:04PM
(#6395121)
Hey Ben,
Author of go-workers here. On SIGTERM, I stop accepting new work, and wait for all running workers to finish before halting.
If workers take longer than the 10 seconds Heroku gives you, go-workers uses reliable queueing (using http://redis.io/commands/brpoplpush) so the job will run again next time you start up the process.
Re:Show HN: goworker – a faster, Resque-compatible backgroun...
by benmanns on Monday September 16, 2013 @03:36PM
(#6395358)
Okay, cool. I do the same thing on the polling side, but don't use reliable queueing yet. I think that is probably the best way to handle the failures.
Author of go-workers here. On SIGTERM, I stop accepting new work, and wait for all running workers to finish before halting.
If workers take longer than the 10 seconds Heroku gives you, go-workers uses reliable queueing (using http://redis.io/commands/brpoplpush) so the job will run again next time you start up the process.