cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Arun KMPtin (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CASSANDRA-10042) Enabling Virtural Node causes data shortage from new DC
Date Tue, 11 Aug 2015 12:31:46 GMT

     [ https://issues.apache.org/jira/browse/CASSANDRA-10042?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Arun KMPtin updated CASSANDRA-10042:
------------------------------------
    Description: 
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.
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.
After rebuild i update keys
>From new data center unavailability start from rebuild nodes in new data center. After
decommission nodes in old data center every thing comes normal.



  was:
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.
As per the above step the i starts to migrate cassandra from initial token to virtual node.
But in between i found data unavailability from my hector client.
Unavailability start from procedure 2( When i starts pointing client to new data center) to
decommissioning old data center. In between i found data unavailability.




> 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
>             Fix For: 2.0.x
>
>
> 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.
> 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.
> After rebuild i update keys
> 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)

Mime
View raw message