[
https://issues.apache.org/jira/browse/CASSANDRA-1304?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Ellis resolved CASSANDRA-1304.
---------------------------------------
Resolution: Duplicate
I believe this is the same as CASSANDRA-1291, assuming you're using trunk. (If
you're not using trunk, you shouldn't be using DatacenterShardStrategy.)
> DatacenterShardStrategy nodetool ring command shows incorrect/duplicate nodes
> -----------------------------------------------------------------------------
>
> Key: CASSANDRA-1304
> URL: https://issues.apache.org/jira/browse/CASSANDRA-1304
> Project: Cassandra
> Issue Type: Bug
> Components: Core
> Reporter: Jignesh Dhruv
>
> Hello,
> We are planning to use DatacenterShardStrategy for our application. In
> cassandra-rack.properties file we define the IP address and the RACK
> information for each machine and in datacenters.properties we define how many
> copies needs to be created in each datacenter.
> When we load the data, correct copies gets created in each datacenter however
> when we run the ring command using nodeTool, we do not see all the nodes in
> the cluster.
> Say we have 2 DC's and each DC has 5 machines, and one data copy in each
> datacenter. Now when we run the ring command we see 7 machines from DC1 and 3
> from DC2. i.e. same node from DC1 gets displayed twice or thrice with a
> different key address.
> I believe this is eventually creating problem as the data is not balanced
> properly within a datacenter.
> Also at times when we run nodeTool-loadBalance data gets moved from one
> datacenter to another instead of being balanced within the same datacenter.
> Can you please look into this issue?
> Thanks,
> Jignesh
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
