Hi Daniel,
target_n_val can be changed at any time and will take effect at the first
iteration of the claim algorithm [0] (which usually runs whenever you
add/remove nodes from the cluster via the riak-admin command)
On default settings, Riak is able to replicate data to distinct nodes in
all clu
Hi Ciprian
Thanks for reply
I'm assuming 'overlay' you are talking about are vnodes?
When creating cluster and joining 2 nodes to first node (3-node cluster)
there should be possible distributing partitions to guarantee 3 copies are
on distinct machines. Simple sequential vnode assignment would do
Hi Daniel,
"A Little Riak Book" covers the logic behind partition allocation in an
overly simplified way.
Riak will distribute partitions to vnodes in a pseudo-random fashion,
resulting in allocations like you described. These allocations are less
optimal when the number of riak nodes are small,
