Re:

You need to email user-unsubscr...@cassandra.apache.org if you don't want to receive emails anymore. Cheers! On Thu, Jan 23, 2020 at 3:12 AM Sowjanya Karangula wrote: > stop >

Re: Is there any concern about increasing gc_grace_seconds from 5 days to 8 days?

I have plans to do so in the near-ish future. People keep adding things to my to-do list, and I don’t have something on my to-do list yet saying “stop people from adding things to my to-do list”. 😉 Assuming I get to that point, if I answer something and I think something I wrote is relevant,

Re: Is there any concern about increasing gc_grace_seconds from 5 days to 8 days?

Thanks for the explanation. It should deserve a blog post Sergio On Wed, Jan 22, 2020, 1:22 PM Reid Pinchback wrote: > The reaper logs will say if nodes are being skipped. The web UI isn’t > that good at making it apparent. You can sometimes tell it is likely > happening when you see time gap

Re: Is there any concern about increasing gc_grace_seconds from 5 days to 8 days?

The reaper logs will say if nodes are being skipped. The web UI isn’t that good at making it apparent. You can sometimes tell it is likely happening when you see time gaps between parts of the repair. This is for when nodes are skipped because of a timeout, but not only that. The gaps are mo

Re: Is there any concern about increasing gc_grace_seconds from 5 days to 8 days?

Thank you very much for your extended response. Should I look in the log some particular message to detect such behavior? How do you tune it ? Thanks, Sergio On Wed, Jan 22, 2020, 12:59 PM Reid Pinchback wrote: > Kinda. It isn’t that you have to repair twice per se, just that the > possibility

Re: Is there any concern about increasing gc_grace_seconds from 5 days to 8 days?

Kinda. It isn’t that you have to repair twice per se, just that the possibility of running repairs at least twice before GC grace seconds elapse means that clearly there is no chance of a tombstone not being subject to repair at least once before you hit your GC grace seconds. Imagine a tombsto

Re: Is there any concern about increasing gc_grace_seconds from 5 days to 8 days?

I was wondering if I should always complete 2 repairs cycles with reaper even if one repair cycle finishes in 7 hours. Currently, I have around 200GB in column family data size to be repaired and I was scheduling once repair a week and I was not having too much stress on my 8 nodes cluster with i3

Re: Is there any concern about increasing gc_grace_seconds from 5 days to 8 days?

Thank you very much! Yes I am using reaper! Best, Sergio On Wed, Jan 22, 2020, 8:00 AM Reid Pinchback wrote: > Sergio, if you’re looking for a new frequency for your repairs because of > the change, if you are using reaper, then I’d go for repair_freq <= > gc_grace / 2. > > > > Just serendipit

[no subject]

stop

Re: Is there any concern about increasing gc_grace_seconds from 5 days to 8 days?

Sergio, if you’re looking for a new frequency for your repairs because of the change, if you are using reaper, then I’d go for repair_freq <= gc_grace / 2. Just serendipity with a conversation I was having at work this morning. When you actually watch the reaper logs then you can see situations

Re: Cassandra2.0.14 : Obsolete files not being deleted after compaction

Thanks Jeff. There was no restart between "Compacting" and "Compacted" logs but I observed that full repair (-pr) was running at that time with errors. *Caused by: java.lang.RuntimeException: java.io.IOException: Cannot proceed on repair because a neighbor (/aa.bb.cc.dd) is dead: session failed*