Yes, that's what I am looking for. Thanks.
On Mon, Jul 15, 2013 at 10:08 PM, Jake Luciani wrote:
> Take a look at https://issues.apache.org/jira/browse/CASSANDRA-5661
>
>
> On Mon, Jul 15, 2013 at 4:18 AM, sulong wrote:
>
>> Thanks for your help. Yes, I will try to
STables one level down to make them compact
> earlier without avoiding the
> "OMG-must-compact-everything-aargh-my-L0-is-full" -effect of removing the
> JSON file.
>
> /Janne
>
> On 15 Jul 2013, at 10:48, sulong wrote:
>
> > Why does cassandra PoolingSegmente
Why does cassandra PoolingSegmentedFile recycle the RandomAccessReader? The
RandomAccessReader objects consums too much memory.
I have a cluster of 4 nodes. Every node's cassandra jvm has 8G heap. The
cassandra's memory is full after about one month, so I have to restart the
4 nodes every month.
one SStable.
>
> Cheers
>
> -
> Aaron Morton
> Freelance Cassandra Consultant
> New Zealand
>
> @aaronmorton
> http://www.thelastpickle.com
>
> On 28/06/2013, at 6:23 PM, sulong wrote:
>
> Total 100G data per node.
>
>
> On Fri, Jun 28, 2013 at 2:14 PM, s
Total 100G data per node.
On Fri, Jun 28, 2013 at 2:14 PM, sulong wrote:
> aaron, thanks for your reply. Yes, I do use the Leveled compactions
> strategy, and the SSTable size is 10M. If it happens again, I will try to
> enlarge the sstable size.
>
> I just wonder why cassandr
t;
> If you are running it try using a larger SSTable size like 32MB
>
> Cheers
>
>-
> Aaron Morton
> Freelance Cassandra Consultant
> New Zealand
>
> @aaronmorton
> http://www.thelastpickle.com
>
> On 27/06/2013, at 2:02 PM, sulong wrote
According to the OpsCenter records, yes, the compaction was running then,
8.5mb /s
On Thu, Jun 27, 2013 at 9:54 AM, sulong wrote:
> version: 1.2.2
> cluster read requests 800/s, write request 22/s
> Sorrry, I don't know whether the compaction was running then.
>
>
>
version: 1.2.2
cluster read requests 800/s, write request 22/s
Sorrry, I don't know whether the compaction was running then.
On Thu, Jun 27, 2013 at 1:02 AM, Robert Coli wrote:
> On Tue, Jun 25, 2013 at 10:13 PM, sulong wrote:
> > I have 4 nodes cassandra cluster. Every node
I also encountered similar problem. I dump the jvm heap and analyse it by
eclipse mat. The eclipse plugin told me there are 10334 instances of
SSTableReader, consuming 6.6G memory. I found the CompactionExecutor thread
held 8000+ SSTalbeReader object. I wonder why there are so many
SSTableReader i
