Hi Daniel, One possible configuration would be:
+ fronting the Riak cluster with HAProxy (or a hardware load balancer) + when the Riak server boots-up, block the Riak API ports (using iptables) + also at boot, spawn a riak-admin wait-for-service riak_kv process [0] + once the riak-admin exits, drop the Riak API related rules from iptables Handling failures and retries gracefully in the application code should help as well. [0] http://docs.basho.com/riak/latest/ops/running/tools/riak-admin/#wait-for-service Regards, Ciprian On Wed, Mar 5, 2014 at 12:58 PM, Daniel Iwan <iwan.dan...@gmail.com> wrote: > Any ideas regarding that? > > Thanks > Daniel > > > > -- > View this message in context: > http://riak-users.197444.n3.nabble.com/Cluster-start-and-2i-query-tp4030557p4030610.html > Sent from the Riak Users mailing list archive at Nabble.com. > > _______________________________________________ > 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
