cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Study Hsueh (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-9607) Get high load after upgrading from 2.1.3 to cassandra 2.1.6
Date Thu, 25 Jun 2015 04:13:05 GMT

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

Study Hsueh commented on CASSANDRA-9607:
----------------------------------------

My colleague said he performed the following queries before the whole cluster went down.
1. SELECT * FROM ginger.supply_ad_log -> timeout
2. SELECT rmaxSpaceId FROM Supply_Ad_Log WHERE rmaxSpaceId = ? AND salesChannel = ? AND hourstamp
= ? -> query was hanged and cluster did not have responsed

The client tool was gocql and he did not specify `pagesize` (default: 0).

> 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.x
>
>         Attachments: GC_state.png, cassandra.yaml, client_blocked_thread.png, cpu_profile.png,
dump.tdump, load.png, log.zip, schema.zip, vm_monitor.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)

Mime
View raw message