[
https://issues.apache.org/jira/browse/CASSANDRA-8566?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14275073#comment-14275073
]
Benedict commented on CASSANDRA-8566:
-------------------------------------
Were these commands run during the time covered by cass.log? If so, it looks
like the problem is now different, presumably because the system state has
become unstable due to the prior crash. The node was failing during startup
cleaning up compaction leftovers (this likely needs a separate bug filing to
resolve).
> node crash (while auto-compaction?)
> -----------------------------------
>
> Key: CASSANDRA-8566
> URL: https://issues.apache.org/jira/browse/CASSANDRA-8566
> Project: Cassandra
> Issue Type: Bug
> Environment: Linux CentOS 6.6 64bit, Cassandra 2.1.2 (release)
> Reporter: Dmitri Dmitrienko
> Fix For: 2.1.3
>
> Attachments: 1.log, 1.tar.gz
>
>
> As data size became 20-24GB/node this issue started happening quite
> frequently. With 7GB/node I didn't notice any crashes.
> HEAP size was 10GB, now increased to 16GB and it didn't help.
> Log is attached
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
