incubator-cassandra-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Terje Marthinussen <tmarthinus...@gmail.com>
Subject Re: insufficient space to compact even the two smallest files, aborting
Date Fri, 10 Jun 2011 14:40:51 GMT
Yes, which is perfectly fine for a short time if all you want is to compact
to one file for some reason.

I run min_compaction_threshold = 2 on one system here with SSD. No problems
with the more aggressive disk utilization on the SSDs from the extra
compactions, reducing disk space is much more important.

Note that this is a treshold per bucket of similar sized sstables. Not the
total number of sstables, so a treshold of 2 will not give you one big file.

Terje

On Fri, Jun 10, 2011 at 8:56 PM, Maki Watanabe <watanabe.maki@gmail.com>wrote:

> But decreasing min_compaction_threashold will affect on minor
> compaction frequency, won't it?
>
> maki
>
>
> 2011/6/10 Terje Marthinussen <tmarthinussen@gmail.com>:
> > bug in the 0.8.0 release version.
> > Cassandra splits the sstables depending on size and tries to find (by
> > default) at least 4 files of similar size.
> > If it cannot find 4 files of similar size, it logs that message in 0.8.0.
> > You can try to reduce the minimum required  files for compaction and it
> will
> > work.
> > Terje
> > 2011/6/10 H├ęctor Izquierdo Seliva <izquierdo@strands.com>
> >>
> >> Hi, I'm running a test node with 0.8, and everytime I try to do a major
> >> compaction on one of the column families this message pops up. I have
> >> plenty of space on disk for it and the sum of all the sstables is
> >> smaller than the free capacity. Is there any way to force the
> >> compaction?
> >>
> >
> >
>
>
>
> --
> w3m
>

Mime
View raw message