SV: Is Riak suitable for s small-record write-intensive billion-records application?
jens.rantil at telavox.se
Mon Oct 22 04:23:45 EDT 2012
> Any given node can be stopped or additional nodes can be added with almost no interruption. If the active node is taken down, CARP will appoint a new active node and its front-end will start accepting requests replacing the gone node. New nodes will announce themselves to the front-end apps via multicast.
But CARP only handles when the _machine_ goes down, right? Have you planned for the scenario when if Riak would go down, but the machine would be responsive? If not, haproxy could be an option.
More information about the riak-users