We are planning on running resque (1.19.0) on cedar and saw this thread on orphaned workers: https://github.com/defunkt/resque/issues/319 Seems like there were a few proposed solutions, but no resolution yet.
Is anyone else running resque on cedar? How do you work around the orphaned worker issue?
On Tuesday, 7 February 2012 at 17:30, kowsik wrote: > We are planning on running resque (1.19.0) on cedar and saw this > thread on orphaned workers: > https://github.com/defunkt/resque/issues/319 Seems like there were a > few proposed solutions, but no resolution yet.
> Is anyone else running resque on cedar? How do you work around the > orphaned worker issue?
> -- > You received this message because you are subscribed to the Google Groups "Heroku" group. > To post to this group, send email to heroku@googlegroups.com (mailto:heroku@googlegroups.com). > To unsubscribe from this group, send email to heroku+unsubscribe@googlegroups.com (mailto:heroku+unsubscribe@googlegroups.com). > For more options, visit this group at http://groups.google.com/group/heroku?hl=en.
On Tue, Feb 7, 2012 at 9:34 AM, Neil Middleton <neil.middle...@gmail.com> wrote: > See the comment from @hone about half way down. This branch is working just > fine for us in a few projects.
> -Neil
> Neil
> On Tuesday, 7 February 2012 at 17:30, kowsik wrote:
> We are planning on running resque (1.19.0) on cedar and saw this > thread on orphaned workers: > https://github.com/defunkt/resque/issues/319 Seems like there were a > few proposed solutions, but no resolution yet.
> Is anyone else running resque on cedar? How do you work around the > orphaned worker issue?
> -- > You received this message because you are subscribed to the Google Groups > "Heroku" group. > To post to this group, send email to heroku@googlegroups.com. > To unsubscribe from this group, send email to > heroku+unsubscribe@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/heroku?hl=en.
> -- > You received this message because you are subscribed to the Google Groups > "Heroku" group. > To post to this group, send email to heroku@googlegroups.com. > To unsubscribe from this group, send email to > heroku+unsubscribe@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/heroku?hl=en.
Had a follow up question. How resilient are the resque workers to the periodic cycling that Heroku does?
For example, let's say a worker dequeues a SendEmail job and is in the middle of sending it. For whatever reason this takes longer than 10 seconds and Heroku cycles the dyno. Does the job go into an orphaned state or is there some way to retry/resume the job when the new worker comes up?
> On Tue, Feb 7, 2012 at 9:34 AM, Neil Middleton <neil.middle...@gmail.com> wrote: >> See the comment from @hone about half way down. This branch is working just >> fine for us in a few projects.
>> -Neil
>> Neil
>> On Tuesday, 7 February 2012 at 17:30, kowsik wrote:
>> We are planning on running resque (1.19.0) on cedar and saw this >> thread on orphaned workers: >> https://github.com/defunkt/resque/issues/319 Seems like there were a >> few proposed solutions, but no resolution yet.
>> Is anyone else running resque on cedar? How do you work around the >> orphaned worker issue?
>> -- >> You received this message because you are subscribed to the Google Groups >> "Heroku" group. >> To post to this group, send email to heroku@googlegroups.com. >> To unsubscribe from this group, send email to >> heroku+unsubscribe@googlegroups.com. >> For more options, visit this group at >> http://groups.google.com/group/heroku?hl=en.
>> -- >> You received this message because you are subscribed to the Google Groups >> "Heroku" group. >> To post to this group, send email to heroku@googlegroups.com. >> To unsubscribe from this group, send email to >> heroku+unsubscribe@googlegroups.com. >> For more options, visit this group at >> http://groups.google.com/group/heroku?hl=en.
