For anyone with questions about how repair works, why repair, partial range repair, incremental vs. non-incremental repair, best practices for repair, etc. I highly recommend this talk from Alexander Dejanovski, The Last Pickle at Cassandra Summit 2016:
https://www.youtube.com/watch?v=1Sz_K8UID6E <https://www.youtube.com/watch?v=1Sz_K8UID6E> Alexander went a little too crazy on the auto-repeat animated GIFs, but the information is excellent — thanks Alexander if you’re out there - I really got a lot out of your talk. :-) - Max > On Mar 14, 2017, at 12:48 pm, Thakrar, Jayesh <jthak...@conversantmedia.com> > wrote: > > Thank you for the links, Meg - very helpful! > > From: Meg Mara <mm...@digitalriver.com <mailto:mm...@digitalriver.com>> > Date: Tuesday, March 14, 2017 at 2:08 PM > To: "user@cassandra.apache.org <mailto:user@cassandra.apache.org>" > <user@cassandra.apache.org <mailto:user@cassandra.apache.org>> > Subject: RE: Does "nodetool repair" need to be run on each node for a given > table? > > Yes, whichever node initiates “nodetool repair” becomes the co-ordinator node > for that repair operation and only the token ranges it owns are repaired. > Other nodes which own data in that “repaired token range” will also be > involved in this repair operation, create their merkle trees and send it to > coordinator for comparison. > > There is a lot to explain when it comes to repair and its many options (-pr, > -inc, -par etc). I recommend the following two links which provide the > answers to all your questions. > > https://www.datastax.com/dev/blog/repair-in-cassandra > <https://www.datastax.com/dev/blog/repair-in-cassandra> > https://www.pythian.com/blog/effective-anti-entropy-repair-cassandra/ > <https://www.pythian.com/blog/effective-anti-entropy-repair-cassandra/> > > Thanks, > - Meg Mara > > From: Thakrar, Jayesh [mailto:jthak...@conversantmedia.com > <mailto:jthak...@conversantmedia.com>] > Sent: Tuesday, March 14, 2017 1:26 PM > To: daemeon reiydelle <daeme...@gmail.com <mailto:daeme...@gmail.com>>; > user@cassandra.apache.org <mailto:user@cassandra.apache.org> > Subject: Re: Does "nodetool repair" need to be run on each node for a given > table? > > Thanks Daemon - it’s the documentation that prompted me to ask the question. > > The doc points to further info on incremental, and would I be correct to > interpret that nodetool initiates a repair on a specific node (i.e. the node > specified with -h or the current node)? > > http://www.datastax.com/dev/blog/more-efficient-repairs > <http://www.datastax.com/dev/blog/more-efficient-repairs> > > <image001.png> > > From: daemeon reiydelle <daeme...@gmail.com <mailto:daeme...@gmail.com>> > Date: Monday, March 13, 2017 at 5:02 PM > To: <user@cassandra.apache.org <mailto:user@cassandra.apache.org>> > Subject: Re: Does "nodetool repair" need to be run on each node for a given > table? > > I > find it helpful to read the manual first. After review, I would be happy to > answer specific questions. > > https://docs.datastax.com/en/cassandra/2.1/cassandra/tools/toolsRepair.html > <https://docs.datastax.com/en/cassandra/2.1/cassandra/tools/toolsRepair.html> > > > ....... > > Daemeon C.M. Reiydelle > USA (+1) 415.501.0198 > London (+44) (0) 20 8144 9872 > > On Mon, Mar 13, 2017 at 1:30 PM, Thakrar, Jayesh > <jthak...@conversantmedia.com <mailto:jthak...@conversantmedia.com>> wrote: > I understand that the nodetool command connects to a specific server and for > many of the commands, e.g. "info", "compactionstats", etc, the information is > for that specific node. > While for some other commands like "status", the info is for the whole > cluster. > > So is "nodetool repair" that operates at a single node level (i.e. repairs > the partitions contained on the target node?). > If so, what is the recommended approach to doing repairs? > > E.g. we have a large number of tables (20+), large amount of data (40+ TB) > and a number of nodes (40+). > Do I need to iterate through each server AND each table? > > Thanks, > Jayesh > > > >
