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 rcoli@eventbrite.com
 designates 209.85.216.46 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <B0B3980F-B889-4280-A7D2-E6B3E0886E33@yahoo.com>
References: <E2F98288-6591-4BAC-ACAF-5F46906289B2@yahoo.com>
	<B0B3980F-B889-4280-A7D2-E6B3E0886E33@yahoo.com>
Date: Mon, 23 Sep 2013 15:34:38 -0700
Message-ID: 
 <CAEDUwd3cYrPUJVC0+yNpTaQ16rE9n1Z5AroCCU-Eg+6PxNVU4A@mail.gmail.com>
Subject: Re: Issue with leveled compaction and data migration
From: Robert Coli <rcoli@eventbrite.com>
To: "user@cassandra.apache.org" <user@cassandra.apache.org>
Content-Type: multipart/alternative; boundary=047d7bd76dba22cbdb04e714a056

--047d7bd76dba22cbdb04e714a056
Content-Type: text/plain; charset=ISO-8859-1

On Fri, Sep 13, 2013 at 4:27 AM, Michael Theroux <mtheroux2@yahoo.com>wrote:

> Another question on [the topic of row fragmentation when old rows get a
> large append to their "end" resulting in larger-than-expected bloom
> filters].
>
> Would forcing the table to relevel help this situation?  I believe the
> process to do this on 1.1.X would be to stop cassandra, remove .json file,
> and restart cassandra.  Is this true?
>

I believe forcing a re-level would help, because each row would appear in
fewer sstables and therefore fewer bloom filters.

Yes, that is the process to re-level on Cassandra 1.1.x.

=Rob

--047d7bd76dba22cbdb04e714a056
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">On Fri, Sep 13, 2013 at 4:27 AM, Michael Theroux <span dir=
=3D"ltr">&lt;<a href=3D"mailto:mtheroux2@yahoo.com" target=3D"_blank">mther=
oux2@yahoo.com</a>&gt;</span> wrote:<br><div class=3D"gmail_extra"><div cla=
ss=3D"gmail_quote">
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">Another question on [the topic of row fragme=
ntation when old rows get a large append to their &quot;end&quot; resulting=
 in larger-than-expected bloom filters].<br>

<br>
Would forcing the table to relevel help this situation? =A0I believe the pr=
ocess to do this on 1.1.X would be to stop cassandra, remove .json file, an=
d restart cassandra. =A0Is this true?<br></blockquote><div><br></div><div>
I believe forcing a re-level would help, because each row would appear in f=
ewer sstables and therefore fewer bloom filters.</div><div><br></div><div>Y=
es, that is the process to re-level on Cassandra 1.1.x.</div><div>=A0</div>
<div>=3DRob</div></div></div></div>

--047d7bd76dba22cbdb04e714a056--