Mailing-List: contact user-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@cassandra.apache.org
Received-SPF: pass (athena.apache.org: domain of jonathan.colby@gmail.com
 designates 209.85.214.44 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=content-type:mime-version:subject:from:in-reply-to:date
         :content-transfer-encoding:message-id:references:to:x-mailer;
        b=epTFm5oTIRup9xZeWaDO47uB8/9xSuGWWt+CRYfh4ChJkPUeLb1djTCsBz9ef3Yb6+
         tMK1nuaq29kO+JEd08zwWJm6Iw9+Pi0ibcyVxqBSaZeAk6ereJ1CxH24EDO2PmU1OARV
         32tUsHD4vL+SGVZLFzpenyLaLjZiR5lgiOyiM=
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Apple Message framework v1084)
Subject: Re: insufficient space to compact even the two smallest files,
 aborting
From: Jonathan Colby <jonathan.colby@gmail.com>
In-Reply-To: <74C81686-7AEF-4842-A2D0-3FD0DA11BAEE@thelastpickle.com>
Date: Thu, 23 Jun 2011 10:23:36 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <F5E481EC-659A-472C-B523-F779D49EC286@gmail.com>
References: <1307704586.19401.60.camel@mierdi-laptop>
 <BANLkTimMZfk3+f6mo0Si_9QqgRCy2nypRQ@mail.gmail.com>
 <BANLkTi=eT1k+Opfu8H=-ZcUPnH4Xacn_NQ@mail.gmail.com>
 <BANLkTimFu+n0Wr0Hajc2YxTkxPXaLoUTJw@mail.gmail.com>
 <1307718655.10346.1.camel@mierdi-laptop>
 <1307969934.2758.2.camel@mierdi-laptop>
 <BANLkTinHDPf7Uv9v7K+gtzOvNCMsLLO=Bw@mail.gmail.com>
 <1307976917.2758.5.camel@mierdi-laptop>
 <BANLkTikdxeTP0v_TLyBTwAZaWad6d1+aZA@mail.gmail.com>
 <1308751453.2601.18.camel@mierdi-laptop>
 <74C81686-7AEF-4842-A2D0-3FD0DA11BAEE@thelastpickle.com>
To: user@cassandra.apache.org

A compaction will be triggered when "min" number of same sized SStable =
files are found.   So what's actually the purpose of  the "max" part of =
the threshold?  =20


On Jun 23, 2011, at 12:55 AM, aaron morton wrote:

> Setting them to 2 and 2 means compaction can only ever compact 2 files =
at time, so it will be worse off.
>=20
> Lets the try following:
>=20
> - restore the compactions settings to the default 4 and 32
> - run `ls -lah` in the data dir and grab the output
> - run `nodetool flush` this will trigger minor compaction once the =
memtables have been flushed
> - check the logs for messages from 'CompactionManager'
> - when done grab the output from  `ls -lah` again.=20
>=20
> Hope that helps.=20
>=20
>=20
> -----------------
> Aaron Morton
> Freelance Cassandra Developer
> @aaronmorton
> http://www.thelastpickle.com
>=20
> On 23 Jun 2011, at 02:04, H=E9ctor Izquierdo Seliva wrote:
>=20
>> Hi All. I set the compaction threshold at minimum 2, maximum 2 and =
try
>> to run compact, but it's not doing anything. There are over 69 =
sstables
>> now, read performance is horrible, and it's taking an insane amount =
of
>> space. Maybe I don't quite get how the new per bucket stuff works, =
but I
>> think this is not normal behaviour.
>>=20
>> El lun, 13-06-2011 a las 10:32 -0500, Jonathan Ellis escribi=F3:
>>> As Terje already said in this thread, the threshold is per bucket
>>> (group of similarly sized sstables) not per CF.
>>>=20
>>> 2011/6/13 H=E9ctor Izquierdo Seliva <izquierdo@strands.com>:
>>>> I was already way over the minimum. There were 12 sstables. Also, =
is
>>>> there any reason why scrub got stuck? I did not see anything in the
>>>> logs. Via jmx I saw that the scrubbed bytes were equal to one of =
the
>>>> sstables size, and it stuck there for a couple hours .
>>>>=20
>>>> El lun, 13-06-2011 a las 22:55 +0900, Terje Marthinussen escribi=F3:
>>>>> That most likely happened just because after scrub you had new =
files
>>>>> and got over the "4" file minimum limit.
>>>>>=20
>>>>> https://issues.apache.org/jira/browse/CASSANDRA-2697
>>>>>=20
>>>>> Is the bug report.
>>>>>=20
>>>>=20
>>>>=20
>>>>=20
>>>>=20
>>>=20
>>>=20
>>>=20
>>=20
>>=20
>=20