[
https://issues.apache.org/jira/browse/CASSANDRA-8800?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Philip Thompson resolved CASSANDRA-8800.
----------------------------------------
Resolution: Cannot Reproduce
Without the ability to reproduce the issue, it is impossible to tell if this
was a simple corruption solvable by nodetool scrub.
> 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)
