anks again,
Chris
From: Dan Washusen [mailto:d...@reactive.org]
Sent: 22 September 2010 09:11
To: user@cassandra.apache.org
Subject: Re: Running out of heap
A key point in that FAQ entry is that the deletes don't occur until
after the configured GCGraceSeconds (10 days is the de
I
> see is the usage grow then shrink, but it despite the periodic compaction
> the overall result is a slow but steady growth.
>
>
>
> Regards,
>
>
>
> Chris
>
>
>
> *From:* Dan Washusen [mailto:d...@reactive.org]
> *Sent:* 22 September 2010 08:39
September 2010 08:39
To: user@cassandra.apache.org
Subject: Re: Running out of heap
http://wiki.apache.org/cassandra/FAQ#i_deleted_what_gives
That help?
On Wed, Sep 22, 2010 at 5:27 PM, Chris Jansen
wrote:
Hi all,
I have written a test application that does a write, read and delete on
one
Thanks Leo, I'll have a read.
Regards,
Chris
From: Matthias L. Jugel [mailto:l...@thinkberg.com]
Sent: 22 September 2010 08:39
To: user@cassandra.apache.org
Subject: Re: Running out of heap
We had similar problems. It may help to read this:
http://blog.mikiobraun.de/ (Tuni
http://wiki.apache.org/cassandra/FAQ#i_deleted_what_gives
That help?
On Wed, Sep 22, 2010 at 5:27 PM, Chris Jansen <
chris.jan...@cognitomobile.com> wrote:
> Hi all,
>
>
>
> I have written a test application that does a write, read and delete on one
> of the sample column families that ship with
We had similar problems. It may help to read this:
http://blog.mikiobraun.de/ (Tuning GC for Cassandra)
Regards,
Leo.
On 22.09.2010, at 09:27, Chris Jansen wrote:
> Hi all,
>
> I have written a test application that does a write, read and delete on one
> of the sample column families that s
On Tue, Jul 20, 2010 at 1:28 PM, Peter Schuller
wrote:
>> Attaching Jconsole shows that there is a growth of memory and weird
>> spikes. Unfortunately I did not take a screen shot of the growth of
>> the spike over time. I'll do that when it occurs again.
>
> Note that expected behavior for CMS is
> Attaching Jconsole shows that there is a growth of memory and weird
> spikes. Unfortunately I did not take a screen shot of the growth of
> the spike over time. I'll do that when it occurs again.
Note that expected behavior for CMS is to have lots of small ups and
downs as a result of young gene
The storage structure is rather simple.
For every 1 key there is 1 column and a timestamp for that column.
We don't enable pulling a huge amount of data and all other nodes are
up servicing the same request. I suspect there may be another problem
with Memory management inside Cassandra.
Attac
On Tue, Jul 20, 2010 at 9:09 PM, Peter Schuller
wrote:
>> CassandraDaemon.java (line 83) Uncaught exception in thread
>> Thread[pool-1-thread-37895,5,main]
>> java.lang.OutOfMemoryError: Java heap space
>> at
>> org.apache.thrift.protocol.TBinaryProtocol.readStringBody(TBinaryProtocol.jav
> CassandraDaemon.java (line 83) Uncaught exception in thread
> Thread[pool-1-thread-37895,5,main]
> java.lang.OutOfMemoryError: Java heap space
> at
> org.apache.thrift.protocol.TBinaryProtocol.readStringBody(TBinaryProtocol.java:296)
> at
> org.apache.thrift.protocol.TBinaryProt
INFO [HINTED-HANDOFF-POOL:1] 2010-07-20 15:10:43,721
HintedHandOffManager.java (line 210) Finished hinted handoff of 0 rows
to endpoint /10.129.28.23
ERROR [pool-1-thread-37895] 2010-07-20 15:10:51,622
CassandraDaemon.java (line 83) Uncaught exception in thread
Thread[pool-1-thread-37895,5,main]
j
12 matches
Mail list logo
