> …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 > 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. > Is there anything I'm missing ? Look for messages with "session completed" in the log from the AntiEntropyService Cheers ----------------- Aaron Morton Freelance Cassandra Developer New Zealand @aaronmorton http://www.thelastpickle.com On 18/02/2013, at 12:51 AM, Marco Matarazzo <marco.matara...@hexkeep.com> wrote: > 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 line is: > > [2013-02-17 10:20:15,186] Starting repair command #1, repairing 768 ranges > for keyspace goh_master > [2013-02-17 10:48:13,401] Repair session 3d140e10-78e3-11e2-af53-d344dbdd69f5 > for range (6556914650761469337,6580337080281832001] finished > (…repeat the last line 767 times) > > …so it seems to me that it is running on all vnodes ranges. > > Also, whatever the node which I launch the command on is, only one node log > is "moving" and is always the same node. > > So, to me, it's like the "nodetool repair" command is running always on the > same single node and repairing everything. > > I'm sure I'm making some mistakes, and I just can't find any clue of what's > wrong with my nodetool usage on the documentation (if anything is wrong, > btw). Is there anything I'm missing ? > > -- > Marco Matarazzo > >
