You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@cassandra.apache.org by "Philip Thompson (JIRA)" <ji...@apache.org> on 2015/02/13 16:45:11 UTC

[jira] [Updated] (CASSANDRA-8800) Cassandra fails to start with OOM after disk space problem occurred

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

Philip Thompson updated CASSANDRA-8800:
---------------------------------------
    Reproduced In: 2.1.1
    Fix Version/s: 2.1.4

> Cassandra fails to start with OOM after disk space problem occurred
> -------------------------------------------------------------------
>
>                 Key: CASSANDRA-8800
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-8800
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: Maxim Podkolzine
>             Fix For: 2.1.4
>
>
> It one point the Cassandra failed with 
> org.apache.cassandra.io.FSWriteError: java.io.IOException: No space left on device
> Which seems pretty normal situation. But after the disk space was increased, Cassandra refused to start up again. The memory snapshot shows a big ArrayList of org.apache.cassandra.io.sstable.SSTableScanner is allocated, holding around 2.8Gb.
> It looks like the DB is corrupted, but we're not entirely sure.



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