Re: system_distributed.repair_history table

small reminder that unless you have autosnapshot to false in cassandra.yaml, you will need to clear snapshot (nodetool clearsnapshot system_distributed) to actually delete the sstables On Thu, Oct 6, 2016 at 9:25 AM, Saladi Naidu wrote: > Thanks for the response. It makes

Re: system_distributed.repair_history table

Thanks for the response. It makes sense to periodically truncate as it is only for debugging purposes Naidu Saladi On Wednesday, October 5, 2016 8:03 PM, Chris Lohfink wrote: The only current solution is to truncate it periodically. I opened 

Re: system_distributed.repair_history table

The only current solution is to truncate it periodically. I opened https://issues.apache.org/jira/browse/CASSANDRA-12701 about it if interested in following On Wed, Oct 5, 2016 at 4:23 PM, Saladi Naidu wrote: > We are seeing following warnings in system.log, As >

system_distributed.repair_history table

We are seeing following warnings in system.log,  As  compaction_large_partition_warning_threshold_mb  in cassandra.yaml file is as default value 100, we are seeing these warnings 110:WARN  [CompactionExecutor:91798] 2016-10-05 00:54:05,554 BigTableWriter.java:184 - Writing large partition