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 19:14:00 GMT

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

Maitrayee edited comment on CASSANDRA-9610 at 6/18/15 7:13 PM:
---------------------------------------------------------------

In 1.2.19 cluster I have 
CREATE KEYSPACE topology WITH replication = {
  'class': 'NetworkTopologyStrategy',
  'dc1': '2',
  'dc2': '2',
  'dc3': '2'
};


In 2.0.9 cluster I have 
CREATE KEYSPACE topology WITH replication = {
  'class': 'NetworkTopologyStrategy',
  'dc1': '2',
  'dc2': '2'
};

Is num_token ignored when initial_token is set? In out 1.2.19 cluster we have the following
values

num_token:256
initial_token:

no value is specified for initial_token

Initially in 2.0.9 we did not set initial_token. Now I tried with empty setting. Response
time still did not improve


was (Author: maitrayee_c):
In 1.2.19 cluster I have 
CREATE KEYSPACE topology WITH replication = {
  'class': 'NetworkTopologyStrategy',
  'dc1': '2',
  'dc2': '2',
  'dc3': '2'
};


In 2.0.9 cluster I have 
CREATE KEYSPACE topology WITH replication = {
  'class': 'NetworkTopologyStrategy',
  'dc1': '2',
  'dc2': '2'
};

Is num_token ignored when initial_token is set? In out 1.2.19 cluster we have the following
values

num_token:256
initial_token:

no value is specified for initial_toke.

Initially in 2.0.9 we did not set initial_token. Now I tried with empty setting. Response
time still not improve

> 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