On Thu, Nov 28, 2013 at 7:21 PM, Robert Wille wrote:
> So here’s my question. If Cassandra only compacts one table at a time,
> then I should be safe if I keep as much free space as there is data in the
> largest table. If Cassandra can compact multiple tables simultaneously,
> then it seems that
Hi,
> If Cassandra only compacts one table at a time, then I should be safe if
I keep as much free space as there is data in the largest table. If
Cassandra can compact multiple tables simultaneously, then it seems that I
need as much free space as all the tables put together, which means no more
Hi Robert,
We found having about 50% free disk space is a good rule of thumb.
Cassandra will typically use less than that when running compactions,
however it is good to have free space available just in case it compacts
some of the larger SSTables in the keyspace. More information can be found
o
Apart from the compaction, you might want to also look at free space required
for repairs.
This could be problem if you have large rows as repair is not at column level.
> On Nov 28, 2013, at 19:21, Robert Wille wrote:
>
> I’m trying to estimate our disk space requirements and I’m wondering
I¹m trying to estimate our disk space requirements and I¹m wondering about
disk space required for compaction.
My application mostly inserts new data and performs updates to existing data
very infrequently, so there will be very few bytes removed by compaction. It
seems that if a major compaction
