Hi Satoshi,
Incremental Backup if set to True, copies SSTables to the backup folder as
soon as a SSTable is flushed to disk. Hence these backed up SSTables miss
out on the opportunity to go through compaction. Does that explain the
longer time ?
- Rajath
Rajath
Just to followup on this post with a couple of more data points:
1)
We upgraded to 2.2.7 and did not see any change in behavior.
2)
However, what *has* fixed this issue for us was disabling msg coalescing by
setting:
otc_coalescing_strategy: DISABLED
We were using the default setting before
Hello,
I have started Slack channel to discuss Cassandra.
The purpose of this channel to use existing slack platform to get connected
to like minded Cassandra people. You can sign up using
https://cassandra-slack.herokuapp.com/
Looking forward to talk to you on Slack!
--
Thanks and Regards,
Hi Prasenjit
Thank you for your reply.
However, I doubt that incremental backup can reduce RTO. I think the
demerit of incremental backup is to take longer repair time rather than
without incremental backup.
Because I've compared the repair time of two cases like below.
(a) snapshot(10GB, full
