[
https://issues.apache.org/jira/browse/CASSANDRA-9607?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14593716#comment-14593716
]
Robbie Strickland commented on CASSANDRA-9607:
----------------------------------------------
This is interesting, because we are currently troubleshooting these exact
symptoms on our analytics cluster when querying large tables using Spark. We
had suspected sstable corruption, since some tables do work. But size appears
to matter. Further, as I read your comment we had just finished loading one of
the problematic tables into a test cluster running 2.1.4, and the same Spark
job runs problem free. I am quite sure there's a correlation here.
> 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, Oracle JDK 8
> VM: Azure VM Standard A3 * 6
> RAM: 7 GB
> Cores: 4
> Reporter: Study Hsueh
> Assignee: Benedict
> Priority: Critical
> Attachments: cassandra.yaml, load.png, log.zip
>
>
> 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)
