t; INFO [CompactionExecutor:4] 2018-01-09 15:55:04,525
> CompactionManager.java:664 - No files to compact for user defined compaction
>
> The last log means something?
>
> Cheers,
> -Simon
>
> From: wxn...@zjqunshuo.com <mailto:wxn...@zjqunshuo.com>
> Date
decided to use TWCS, and doing the full repair is one of the preparation of
changing to TWCS.
From: Alexander Dejanovski
Date: 2018-01-05 15:17
To: user
Subject: Re: Full repair caused disk space increase issue
Hi Simon,
since Cassandra 2.2, anticompaction is performed in all types of repairs
.
From: Alexander Dejanovski
Date: 2018-01-05 15:17
To: user
Subject: Re: Full repair caused disk space increase issue
Hi Simon,
since Cassandra 2.2, anticompaction is performed in all types of repairs,
except subrange repair.
Given that you have some very big SSTables, the temporary space used by
Hi Simon,
since Cassandra 2.2, anticompaction is performed in all types of repairs,
except subrange repair.
Given that you have some very big SSTables, the temporary space used by
anticompaction (which does the opposite of compaction : read one sstable,
output two sstables) will impact your disk u
Hi All,
In order to evict tombstones, I issued full repair with the command "nodetool
-pr -full". Then the data load size was indeed decreased by 100G for each node
by using "nodetool status" to check. But the actual disk usage increased by
500G for each node. The repair is still ongoing and lea
