cassandra-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Langston, Jim" <>
Subject Re: sstable size ?
Date Thu, 18 Jul 2013 10:28:39 GMT
I saw that msg in the thread, I pulled the git files and it looks
like a suite of tools, do I install them on their own ? do I replace the
current ones ? its production data but I can copy the data to where
I want and experiment.


From: aaron morton <<>>
Reply-To: <<>>
Date: Thu, 18 Jul 2013 21:41:24 +1200
To: <<>>
Subject: Re: sstable size ?

Does this help ?

Can you pull the data off the node so you can test it somewhere safe ?


Aaron Morton
Cassandra Consultant
New Zealand


On 18/07/2013, at 2:20 PM, "Langston, Jim" <<>>

Thanks, this does look like what I'm experiencing. Can someone
post a walkthrough ? The README and the sstablesplit script
don't seem to cover it use in any detail.


From: Colin Blower <<>>
Reply-To: <<>>
Date: Wed, 17 Jul 2013 16:49:59 -0700
To: "<>" <<>>
Subject: Re: sstable size ?

Take a look at the very recent thread called 'Alternate "major compaction"'. There are some
ideas in there about splitting up a large SSTable.

On 07/17/2013 04:17 PM, Langston, Jim wrote:
Hi all,

Is there a way to get an SSTable to a smaller size ? By this I mean that I
currently have an SSTable that is nearly 1.2G, so that subsequent SSTables
when they compact are trying to grow to that size. The result is that when
the min_compaction_threshold reaches it value and a compaction is needed,
the compaction is taking a long time as the file grows (it is currently at 52MB and
takes ~22s to compact).

I'm not sure how the SSTable initially grew to its current size of 1.2G, since the
servers have been up for a couple of years. I hadn't noticed until I just upgraded to 1.2.6,
but now I see it affects everything.


Colin Blower
Software Engineer
Barracuda Networks Inc.
+1 408-342-5576 (o)

View raw message