> So, running it periodically on just one node is enough for cluster
> maintenance ?
In the special case where you have RF == Number of nodes.
The recommended approach is to use -pr and run it on each node periodically.
> Also: running it with -pr does output:
That does not look right. There
>> So, to me, it's like the "nodetool repair" command is running always on the
>> same single node and repairing everything.
> If you use nodetool repair without the -pr flag in your setup (3 nodes and I
> assume RF 3) it will repair all token ranges in the cluster.
That's correct, 3 nodes and
> …so it seems to me that it is running on all vnodes ranges.
Yes.
> Also, whatever the node which I launch the command on is, only one node log
> is "moving" and is always the same node.
Not sure what you mean here.
> So, to me, it's like the "nodetool repair" command is running always on the
I'm a bit late, but for reference.
Repair runs in two stages, first differences are detected. You an monitor the
validation compaction with nodetool compactionstats.
Then the differences are streamed between the nodes, you can monitor that with
nodetool netstats.
> Nodetool repair command h
Greetings.
I'm trying to run "nodetool repair" on a Cassandra 1.2.1 cluster of 3 nodes
with 256 vnodes each.
On a pre-1.2 cluster I used to launch a "nodetool repair" on every node every
24hrs. Now I'm getting a differenf behavior, and I'm sure I'm missing something.
What I see on the command
Hi,
I am new to Cassandra and I would like to hear your thoughts on this.
We are running our tests with Cassandra 1.2.1, in relatively small dataset
~60GB.
Nodetool repair command has been running for almost 24hours and I can't see
any activity from the logs or JMX.
What am I missing? Or th
