You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Jonathan Ellis (JIRA)" <ji...@apache.org> on 2015/08/24 18:16:46 UTC
[jira] [Resolved] (CASSANDRA-10042) Enabling Virtural Node causes
data shortage from new DC
[ https://issues.apache.org/jira/browse/CASSANDRA-10042?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jonathan Ellis resolved CASSANDRA-10042.
----------------------------------------
Resolution: Cannot Reproduce
Fix Version/s: (was: 2.0.x)
Closing out 2.0. Please reopen if you can reproduce in 2.1+
> Enabling Virtural Node causes data shortage from new DC
> -------------------------------------------------------
>
> Key: CASSANDRA-10042
> URL: https://issues.apache.org/jira/browse/CASSANDRA-10042
> Project: Cassandra
> Issue Type: Bug
> Components: API, Drivers (now out of tree)
> 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
>
> I followed this Link http://docs.datastax.com/en/cassandra/2.0/cassandra/configuration/configVnodesProduction_t.html to enable virtual node in existing Data Center.
> Data continuously writing in to cassandra.
> After rebuild nodes in new data center, all nodes in new data center gains data.
> As per the above step i starts to migrate cassandra from initial token to virtual node. But in between i found data ( Data which added after rebuild) is unavailable from new data center.
> From new data center unavailability start from rebuild nodes in new data center. After decommission nodes in old data center every thing comes normal.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)