Cassandra tracks it and no new hints will be created once the default 3 hours window is passed . However , cassandra will not automatically trigger a repair if your node is down for more than 3 hours .Default settings of 3 hours for hints is defined in cassandra.yaml file . Look for "max_hint_window_in_ms" in the cassandra.yaml file. Its configurable . Apart from the periodic repair you should start a repair when you bring up a node which has missed some writes .
One more thing is if node is down for long time and missed a lot of writes sometimes it may be better to add that as a new fresh node rather than adding it and then doing repair . On Mon, Apr 8, 2019 at 4:49 PM Stefan Miklosovic < stefan.mikloso...@instaclustr.com> wrote: > Ah I see it is the default for hinted handoffs. I was somehow thinking > its bigger figure I do not know why :) > > I would say you should run repairs continuously / periodically so you > would not even have to do some thinking about that and it should run > in the background in a scheduled manner if possible. > > Regards > > On Tue, 9 Apr 2019 at 04:19, Kunal <kunal.v...@gmail.com> wrote: > > > > Hello everyone.. > > > > > > > > I have a 6 node Cassandra datacenter, 3 nodes on each datacenter. If one > of the node goes down and remain down for more than 3 hr, I have to run > nodetool repair. Just wanted to ask if Cassandra automatically tracks the > time when one of the Cassandra node goes down or do I need to write code to > track the time and run repair when node comes back online after 3 hrs. > > > > > > Thanks in anticipation. > > > > Regards, > > Kunal Vaid > > --------------------------------------------------------------------- > To unsubscribe, e-mail: user-unsubscr...@cassandra.apache.org > For additional commands, e-mail: user-h...@cassandra.apache.org > >
