It helps, Thanks a lot,
miriam
On Mon, Feb 28, 2011 at 9:50 PM, Aaron Morton wrote:
> I thought there was more to it.
>
> The steps for move or removing nodes are outlined on the operations page
> wiki as you probably know.
>
> What approach are you considering to rebalancing the token distribut
I thought there was more to it.
The steps for move or removing nodes are outlined on the operations page wiki
as you probably know.
What approach are you considering to rebalancing the token distribution when
removing a node? E.g. If you have 5 nodes and remove 1 the best long term
solution is
Aaron,
Thanks a lot,
Actually I meant a larger number of nodes than 3 and replication factor of
3.
We are looking on a system that may shrink due to permanent failures, and
then automatically detects the failure and stream its range to other nodes
in the cluster to have again 3 replicas.
I understn
AFAIK the general assumption is that you will want to repair the node manually,
within the GCGraceSeconds period. If this cannot be done then nodetool
decomission and removetoken are the recommended approach.
In your example though, with 3 nodes and an RF of 3 your cluster can sustain a
single
Hi,
I have a question about a tool or a wrapper that perform automatic data move
upon node failure?
Assuming I have 3 nodes with a replication factor of 3. In case of one node
failure, does the third replica (that was located before on the failed node
) re-appears on one the of live nodes?
I am lo
