try specify the InitialToken.
In your cluster, set the token to i*(2**127/6), i = [1,6]. It will helps.
On Sat, May 1, 2010 at 8:03 AM, elsif wrote:
> I upgraded to 0.6.1 and was able to bring up all the nodes and make
> queries.
>
> After adding some new data, the java vm ran out of memory on t
I upgraded to 0.6.1 and was able to bring up all the nodes and make
queries.
After adding some new data, the java vm ran out of memory on three of
the nodes. Cassandra continues to run for about 20 minutes before it
exits completely:
DEBUG [ROW-MUTATION-STAGE:2] 2010-04-30 16:02:27,298
RowMutati
0.5 has a bug that allows it to OOM itself from replaying the log too
fast. You should upgrade to 0.6.1.
On Mon, Apr 26, 2010 at 12:11 PM, elsif wrote:
>
> Hello. I have a six node cassandra cluster running on modest hardware
> with 1G of heap assigned to cassandra. After inserting about 245
>
Hello. I have a six node cassandra cluster running on modest hardware
with 1G of heap assigned to cassandra. After inserting about 245
million rows of data, cassandra failed with a
java.lang.OutOfMemoryError: Java heap space error. I rasied the java
heap to 2G, but still get the same error when
