I am not sure I fully understand the question, because nodetool repair is one of the three ways for Cassandra to ensure consistency. If by "affect" you mean "make your data consistent and ensure all replicas are up-to-date", then yes, that's what I think it does.
And yes, I would expect nodetool repair (especially depending on the options appended to it) to have a performance impact, but how big that impact is going to be depends on many things. We currently perform no scheduled repairs because of our workload and the consistency level that we use. So, as you can understand I am certainly not the best person to analyse that bit... Regards, Vasilis On Sat, Oct 24, 2015 at 5:09 PM, Ajay Garg <ajaygargn...@gmail.com> wrote: > Thanks a ton Vasileios !! > > Just one last question :: > Does running "nodetool repair" affect the functionality of cluster for > current-live data? > > It's ok if the insertions/deletions of current-live data become a little > slow during the process, but data-consistency must be maintained. If that > is the case, I think we are good. > > > Thanks and Regards, > Ajay > > On Sat, Oct 24, 2015 at 6:03 PM, Vasileios Vlachos < > vasileiosvlac...@gmail.com> wrote: > >> Hello Ajay, >> >> Here is a good link: >> >> http://docs.datastax.com/en/cassandra/2.1/cassandra/operations/opsRepairNodesManualRepair.html >> >> Generally, I find the DataStax docs to be OK. You could consult them for >> all usual operations etc. Ofc there are occasions where a given concept is >> not as clear, but you can always ask this list for clarification. >> >> If you find that something is wrong in the docs just email them (more >> info and contact email here: http://docs.datastax.com/en/ ). >> >> Regards, >> Vasilis >> >> On Sat, Oct 24, 2015 at 1:04 PM, Ajay Garg <ajaygargn...@gmail.com> >> wrote: >> >>> Thanks Vasileios for the reply !!! >>> That makes sense !!! >>> >>> I will be grateful if you could point me to the node-repair command for >>> Cassandra-2.1.10. >>> I don't want to get stuck in a wrong-versioned documentation (already >>> bitten once hard when setting up replication). >>> >>> Thanks again... >>> >>> >>> Thanks and Regards, >>> Ajay >>> >>> On Sat, Oct 24, 2015 at 4:14 PM, Vasileios Vlachos < >>> vasileiosvlac...@gmail.com> wrote: >>> >>>> Hello Ajay, >>>> >>>> Have a look in the *max_hint_window_in_ms* : >>>> >>>> >>>> http://docs.datastax.com/en/cassandra/2.0/cassandra/configuration/configCassandra_yaml_r.html >>>> >>>> My understanding is that if a node remains down for more than >>>> *max_hint_window_in_ms*, then you will need to repair that node. >>>> >>>> Thanks, >>>> Vasilis >>>> >>>> On Sat, Oct 24, 2015 at 7:48 AM, Ajay Garg <ajaygargn...@gmail.com> >>>> wrote: >>>> >>>>> If a node in the cluster goes down and comes up, the data gets synced >>>>> up on this downed node. >>>>> Is there a limit on the interval for which the node can remain down? >>>>> Or the data will be synced up even if the node remains down for >>>>> weeks/months/years? >>>>> >>>>> >>>>> >>>>> -- >>>>> Regards, >>>>> Ajay >>>>> >>>> >>>> >>> >>> >>> -- >>> Regards, >>> Ajay >>> >> >> > > > -- > Regards, > Ajay >
