cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tyler Hobbs (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-9610) Increased response time with cassandra 2.0.9 from 1.2.19
Date Wed, 17 Jun 2015 19:26:01 GMT

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

Tyler Hobbs commented on CASSANDRA-9610:
----------------------------------------

It looks like your 1.2 cluster does not have vnodes enabled (num_tokens = 1) and the 2.0 cluster
does.  In 2.1 we've improved the performance when vnodes are enabled with CASSANDRA-1337,
but 2.0 doesn't have this improvement.  I suggest these options:
* Structure your data model so that you don't rely on secondary indexes for queries where
performance matters,
* Upgrade to 2.1, or
* Don't enable vnodes in 2.0

> Increased response time with cassandra 2.0.9 from 1.2.19
> --------------------------------------------------------
>
>                 Key: CASSANDRA-9610
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-9610
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: Maitrayee
>         Attachments: servicedefinition_schema.txt, traceout_1.2.19, traceout_2.0.9
>
>
> I was using Cassandra 1.2.19. Recently upgraded to 2.0.9. Queries with secondary index
was completing much faster in 1.2.19
> Validated this with trace on via cqlsh



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message