You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Aleksey Yeschenko (JIRA)" <ji...@apache.org> on 2015/08/19 17:26:45 UTC
[jira] [Resolved] (CASSANDRA-10054) Enabling Virtual Node unable to
read data in new data center?
[ https://issues.apache.org/jira/browse/CASSANDRA-10054?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Aleksey Yeschenko resolved CASSANDRA-10054.
-------------------------------------------
Resolution: Invalid
Fix Version/s: (was: 2.0.3)
> Enabling Virtual Node unable to read data in new data center?
> -------------------------------------------------------------
>
> Key: CASSANDRA-10054
> URL: https://issues.apache.org/jira/browse/CASSANDRA-10054
> Project: Cassandra
> Issue Type: Bug
> Components: API, Config, Core
> Environment: Linux OS, 2GB RAM, 180 GB Hard Disk
> DC1(Old) - 3 Nodes
> DC2(New) - 3 Nodes
> All machine have same configuration
> Reporter: Arun KMPtin
>
> Im using Cassandra 2.0.3 in Initial Token.
> Having one data center(DC1) with three nodes.
> Now wants to convert from Initial Token to Virtual Token so i follow the instructions noted Enabling virtual nodes on an existing production cluster
> And i used Hector Client with Consistency level LOCAL_QUORUM for read and wirte.
> After i change all configuration files when i UP single node in DC2 from Hector Client i can't read existing data but i can write data. And I can read the newly written data.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)