Benedict commented on CASSANDRA-7220:

[~rarudduck] it looks like the issue that killed your server was OOM. I can't 
see a reason for this in the logs, so it's possible you simply need to increase 
your heap size, however upgrading may help as there are a LOT of exceptions 
related to CASSANDRA-7756 logged, and it's possible that's somehow causing a 
knock on effect of some kind.

> Nodes hang with 100% CPU load
> -----------------------------
>                 Key: CASSANDRA-7220
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-7220
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>         Environment: C* 2.0.7
> 4 nodes cluster on 12 core machines
>            Reporter: Robert Stupp
>            Assignee: Ryan McGuire
>         Attachments: c-12-read-100perc-cpu.zip, system.log
> I've ran a test that both reads and writes rows.
> After some time, all writes succeeded and all reads stopped.
> Two of the four nodes have 16 of 16 threads of the "ReadStage" thread pool 
> running. The number of pending task continuouly grows on these nodes.
> I have attached outputs of the stack traces and some diagnostic output from 
> "nodetool tpstats"
> "nodetool status" shows all nodes as UN.
> I had run that test previously without any issues in with the same 
> configuration.
> Some "specials" from cassandra.yaml:
> - key_cache_size_in_mb: 1024
> - row_cache_size_in_mb: 8192
> The nodes running at 100% CPU are "node2" and "node3". node1&node4 are fine.
> I'm not sure if it is reproducable - but it's definitly not a good behaviour.

This message was sent by Atlassian JIRA

Reply via email to