Peter,
wrote my replies inline.
Mathias Meyer
Developer Advocate, Basho Technologies
On Freitag, 13. Mai 2011 at 20:05, Peter Fales wrote:
> Sean,
>
> Thanks to you and Ben for clarifying how that works. Since that was
> so helpful, I'll ask a followup question, and also a question on
> a m
Sean,
Thanks to you and Ben for clarifying how that works. Since that was
so helpful, I'll ask a followup question, and also a question on
a mostly un-related topic...
1) When I've removed a couple of nodes and the remaining nodes pick up
the slack, is there any way for me to look under the h
Peter,
You've hit on a major feature of Riak: to be available in the face of network
and hardware failure.
When a node is down, other nodes (ones that do not "own" the replicas for a
given key) will pick up the slack and serve read and write requests on behalf
of the downed node. This means
Here is my understanding. Corrections welcome.
You're missing that Riak is happy to be "eventually consistent". Drop
out 2 of your nodes, and it rebalances who is responsible for what,
then under the hood migrates and replicates its data more leisurely.
Data is still being written to 4 differen
