Sean McDaniel

Wait what? Redis can become unavailable? Been away from Node for a while but I see that there is [retry logic](https://github.com/NodeRedis/node_redis/blob/master/index.js#L522) built into node_redis. Off the top of my head...

Found a solution fairly quickly. First resque needs to listen for the `error` event which is [required](https://github.com/NodeRedis/node_redis#error) to ensure the Node process doesn't exit. Then we just need to check...

Good suggestion @evantahler. For projects that need a more robust infrastructure that is route that I would go with. Maybe I should look at ioredis for users who need this...

It is not, but ruby resque does this too I believe. I think this feature is really to allow you too see what worker is running if you were use...

@momow Were you able to verify that the process title is the actual problem on heroku?

Thanks for digging a little deeper. I'll look into this in further detail.

So I tried this locally with foreman v0.57.0 and node v0.8.8 using @momow's code above as an example. I receive the `SIGTERM` in the node process when I issue a...

So is it you can't get the complete process title or is the node process hanging? The distinction is important. Don't rely on the process title from coffee-resque for monitoring...

Once we get some tests we can setup a travis build and test against multiple versions of node I believe.

I'm assuming that you mean the ruby process the runs the web app / worker was consuming this memory. There are couple of parts to this and I just want...