cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robbie Strickland (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (CASSANDRA-9607) Get high load after upgrading from 2.1.3 to cassandra 2.1.6
Date Mon, 22 Jun 2015 14:25:01 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-9607?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14595975#comment-14595975
] 

Robbie Strickland edited comment on CASSANDRA-9607 at 6/22/15 2:24 PM:
-----------------------------------------------------------------------

I did some further testing on this, to at least isolate the affected versions and nail down
steps to reproduce.  I started with a test cluster, 3 x i2.4xlarge instances running 2.1.4
and Spark 1.2.2.  I loaded a few sstables (using sstableloader) from one of my problematic
production tables, and each test involved the following simple statement in the Spark shell:

{code}
sc.cassandraTable("prod_analytics_events", "profileevents").take(100).foreach(println)
{code}

I then upgraded to 2.1.6, loaded about 100G of data, and downgraded back to 2.1.4.  The net
result is that 2.1.4 works with both the small and larger data sets, while 2.1.5 and 2.1.6
work only with only the smaller data sets (the 2.1.5 result comes from my production cluster).
 The larger set caused the hang in both cases.


was (Author: rstrickland):
I did some further testing on this, to at least isolate the affected versions and nail down
steps to reproduce.  I started with a test cluster, 3 x i2.4xlarge instances running 2.1.4
and Spark 1.2.2.  I loaded a few sstables (using sstableloader) from one of my problematic
production tables, and each test involved the following simple statement in the Spark shell:

{code}
sc.cassandraTable("prod_analytics_events", "profileevents").take(100).foreach(println)
{code}

I then upgraded to 2.1.6, loaded about 100G of data, and downgraded back to 2.1.4.  The net
result is that 2.1.4 works with both the small and larger data sets, while 2.1.5 and 2.1.6
work only with only the smaller data sets.  The larger set caused the hang in both cases.

> 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: Tyler Hobbs
>            Priority: Critical
>             Fix For: 2.1.x, 2.2.0 rc2
>
>         Attachments: cassandra.yaml, load.png, log.zip, schema.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)

Mime
View raw message