cassandra-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jack Krupansky <jack.krupan...@gmail.com>
Subject Re: Cassandra OOM on joining existing ring
Date Fri, 10 Jul 2015 11:06:31 GMT
What does your data and data model look like - partition size, rows per
partition, number of columns per row, any large values/blobs in column
values?

You could run fine on an 8GB system, but only if your rows and partitions
are reasonably small. Any large partitions could blow you away.

-- Jack Krupansky

On Fri, Jul 10, 2015 at 4:22 AM, Kunal Gangakhedkar <kgangakhedkar@gmail.com
> wrote:

> Attaching the stack dump captured from the last OOM.
>
> Kunal
>
> On 10 July 2015 at 13:32, Kunal Gangakhedkar <kgangakhedkar@gmail.com>
> wrote:
>
>> Forgot to mention: the data size is not that big - it's barely 10GB in
>> all.
>>
>> Kunal
>>
>> On 10 July 2015 at 13:29, Kunal Gangakhedkar <kgangakhedkar@gmail.com>
>> wrote:
>>
>>> Hi,
>>>
>>> I have a 2 node setup on Azure (east us region) running Ubuntu server
>>> 14.04LTS.
>>> Both nodes have 8GB RAM.
>>>
>>> One of the nodes (seed node) died with OOM - so, I am trying to add a
>>> replacement node with same configuration.
>>>
>>> The problem is this new node also keeps dying with OOM - I've restarted
>>> the cassandra service like 8-10 times hoping that it would finish the
>>> replication. But it didn't help.
>>>
>>> The one node that is still up is happily chugging along.
>>> All nodes have similar configuration - with libjna installed.
>>>
>>> Cassandra is installed from datastax's debian repo - pkg: dsc21 version
>>> 2.1.7.
>>> I started off with the default configuration - i.e. the default
>>> cassandra-env.sh - which calculates the heap size automatically (1/4 * RAM
>>> = 2GB)
>>>
>>> But, that didn't help. So, I then tried to increase the heap to 4GB
>>> manually and restarted. It still keeps crashing.
>>>
>>> Any clue as to why it's happening?
>>>
>>> Thanks,
>>> Kunal
>>>
>>
>>
>

Mime
View raw message