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

Posted to commits@cassandra.apache.org by "Maxim Podkolzine (JIRA)" <ji...@apache.org> on 2015/02/13 12:48:11 UTC

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

Maxim Podkolzine created CASSANDRA-8800:
-------------------------------------------

             Summary: 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


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)