Great, thanks for the feedback. I'll check out pooly, for sure. I was thinking about using HAProxy/Zeus (I'm currently using Riak Smartmachines @ Joyent). I really like this idea, the logic for node failures shouldn't be in my code. I'll give this a try!
Thanks, Marc On Dec 30, 2011, at 11:31 AM, Andrew Berman wrote: > You should look into using HAProxy in front of your nodes. Let HAProxy load > balance between all your nodes and then if one goes down, HAProxy just pulls > it out of the load balancing cluster automatically until it is restored. > Then your pooler can just pool connections from HAProxy instead so it doesn't > have to worry at all about failed nodes. > > Also, shameless plug, I have a pooler as well which has a few more options > than pooler. You can check it out here: https://github.com/aberman/pooly > > --Andrew > > On Fri, Dec 30, 2011 at 9:58 AM, Marc Campbell <m...@look.io> wrote: > Hey all, > > I'm looking for some best practices in handling connections when using the > protocol buffer client. Specifically, I have 3 nodes in my cluster, and need > to figure out how to handle the situation when one of the nodes is down. > > I'm currently using a pooler app (https://github.com/seth/pooler) and this > helps me distribute the load to all of the nodes, but when one goes down, the > app doesn't recover nicely. > > I'm about to write some code in my app to handle this, but before I do, I > thought I'd check for existing solutions and best practices: > > - Is there an existing connection pooling mechanism that someone has created > which handles node failures automatically? > > If not, then I'm looking forward to writing it! > > Thank in advance, > Marc > > _______________________________________________ > riak-users mailing list > riak-users@lists.basho.com > http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com > >
_______________________________________________ riak-users mailing list riak-users@lists.basho.com http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com
