< 2.0 the java cluster client was actively unhelpful (in that it didn't track node health, so if one node was down, the client would regularly try it still, IIRC), and a client-local haproxy (or such) is the way to go.
>= 2.0 the java cluster client looks like it's smarter about tracking node health (but I'm not using it in anger and therefore don't know if it's otherwise suitable and would be curious if anyone is happily using it without haproxy) On Fri, Aug 15, 2014 at 6:18 AM, Paul Barry <paul.ba...@temetra.com> wrote: > We’ve been using Riak with Java client for more than two years in > production, and best solution is ha-proxy. > Your Java client connects to one ha-proxy, configured for round-robin to > all the nodes. We run ha-proxy on our front-ends, so clients always connect > to localhost. > > If you’re planning to add or remove a node, just reconfigure ha-proxy and > reload it (instant with no down-time). > ha-proxy also gives you much better control over how unexpected failures > are dealt with automatically. > > pb > > On 15 Aug 2014, at 13:19, Simon Hartley <simon.hart...@williamhill.com> > wrote: > > Hi, > > So I’m writing a Java client app. I’m running a 5 node Riak cluster and I > want my client to know about all the nodes to avoid single points of > failure. > > Is there a best practice for automatically updating clients when new nodes > are added to a cluster? > > > > > _______________________________________________ > 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
