cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Maitrayee (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (CASSANDRA-9610) Increased response time with cassandra 2.0.9 from 1.2.19
Date Thu, 18 Jun 2015 20:13:01 GMT

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

Maitrayee edited comment on CASSANDRA-9610 at 6/18/15 8:12 PM:
---------------------------------------------------------------

In 1.2.19 I have 3 nodes in each dc. Cluster is across 3 dc
In 2.0.9 I have 2 nodes/dc across 2 dc

As I mentioned, in 1.2.19 initial_token was not set any value, does that still override num_token.
nodetool status on the 1.2.19 cluster shows Tokens as 256

During 1.2.19 to 2.0.9 upgrade initial_token was commented. Do I need to follow the same steps



was (Author: maitrayee_c):
In 1.2.19 I have 3 nodes in each dc. Cluster is across 3 dc

In 2.0.9 I have 2 nodes/dc across 2 dc

> 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