> is this behaviour expected since the RF (for the duration of when 1 node was
> taken out)
> is higher than the # of nodes?
Note that repair is not needed just because a node was off for a while.
I am guessing the performance difference was due to the repair. Try
running repair at any time and s
cheers~
On 7 July 2011 19:41, Watanabe Maki wrote:
> It is expected behaviour and not relate on number of node.
> After the failed node bringing back, the ring will be busy by Hinted
> Handoff rewriting and Read Repair. If you run repair, all your 3 nodes need
> to build Merkel Tree, compare the
It is expected behaviour and not relate on number of node.
After the failed node bringing back, the ring will be busy by Hinted Handoff
rewriting and Read Repair. If you run repair, all your 3 nodes need to build
Merkel Tree, compare the hash values, then transfer latest data to each other.
You
hi guys,
is there a minimum(recommended) number of machines for RF=3?
i encountered a test result where
# of nodes = 3
RF = 3
CL.READ=QUORUM
and when 1 node was taken out and back in after which node repair was run,
the TPS dropped significantly.
is this behaviour expected since the RF (for th
