You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Aleksey Yeschenko (JIRA)" <ji...@apache.org> on 2016/02/05 17:20:39 UTC

[jira] [Updated] (CASSANDRA-11109) Cassandra process killed by OS due to out of memory issue

     [ https://issues.apache.org/jira/browse/CASSANDRA-11109?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Aleksey Yeschenko updated CASSANDRA-11109:
------------------------------------------
    Fix Version/s:     (was: 2.2.4)
                   2.2.x

> Cassandra process killed by OS due to out of memory issue
> ---------------------------------------------------------
>
>                 Key: CASSANDRA-11109
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-11109
>             Project: Cassandra
>          Issue Type: Bug
>         Environment: Operating System: 
> Amazon Linux AMI release 2015.03
> Kernel \r on an \m
> Instance type: m3.2xlarge
> vCPUs: 8
> Memory: 30G
> Commitlog storage: 1 x 80 SSD Storage
> Data disks: EBS io1 300GB with 1000 IOPS
>            Reporter: Tony Xu
>             Fix For: 2.2.x
>
>         Attachments: cassandra-env.txt, cassandra-system-log.txt, cassandra.yaml, system-messages.txt
>
>
> After we upgraded Cassandra from 2.1.12 to 2.2.4 on one of our nodes (A three nodes Cassandra cluster), we've been experiencing an og-going issue with cassandra process running with continuously increasing memory util killed by OOM. 
> {quote}
> Feb  1 23:53:10 kernel: [24135455.025185] [19862]   494 19862 133728623  7379077  139068        0             0 java
> Feb  1 23:53:10 kernel: [24135455.029678] Out of memory: Kill process 19862 (java) score 973 or sacrifice child
> Feb  1 23:53:10 kernel: [24135455.035434] Killed process 19862 (java) total-vm:534918588kB, anon-rss:29413728kB, file-rss:102940kB
> {quote}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)