[
https://issues.apache.org/jira/browse/CASSANDRA-9607?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14591503#comment-14591503
]
Benedict commented on CASSANDRA-9607:
-------------------------------------
I believe there were issues with compactions not being submitted in 2.1.3, so
the upgrade may have triggered your compaction workload to start. In this case,
turning down your concurrent_compactions settings in the yaml would resolve the
problem for you, and let it catch up with compactions.
If that isn't the problem, we would need, preferably, a CPU profile from an
attached debugger, or alternatively a sequence of {{jstack}} and {{top -H -b
-n1}} outputs to analyze. Along with your cassandra.yaml and log file.
> Get high load after upgrading from 2.1.3 to cassandra 2.1.6
> -----------------------------------------------------------
>
> Key: CASSANDRA-9607
> URL: https://issues.apache.org/jira/browse/CASSANDRA-9607
> Project: Cassandra
> Issue Type: Bug
> Environment: OS:
> CentOS 6 * 4
> Ubuntu 14.04 * 2
> JDK: Oracle JDK 7
> Reporter: Study Hsueh
> Priority: Critical
> Attachments: load.png
>
>
> After upgrading cassandra version from 2.1.3 to 2.1.6, the average load of my
> cassandra cluster grows from 0.x~1.x to 3.x~6.x.
> What kind of additional information should I provide for this problem?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
