cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jeremy Hanna (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (CASSANDRA-6320) During range movements, nodetool ring reports incorrect replicas
Date Fri, 08 Nov 2013 17:30:17 GMT

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

Jeremy Hanna edited comment on CASSANDRA-6320 at 11/8/13 5:28 PM:
------------------------------------------------------------------

After that DC completed the balance operation, nodetool ring showed the correct number of
replicas, matching the keyspace metadata again.


was (Author: jeromatron):
After that DC was balanced, nodetool ring showed the correct number of replicas, matching
the keyspace metadata again.

> During range movements, nodetool ring reports incorrect replicas
> ----------------------------------------------------------------
>
>                 Key: CASSANDRA-6320
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-6320
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>            Reporter: Jeremy Hanna
>            Priority: Minor
>
> There are two datacenters and the keyspace configuration for this keyspace is set to
3 in each datacenter.  During a rebalance of the ring, during the range movements, nodetool
ring <keyspace> is reporting that 2 replicas are in the datacenter where movement is
occurring.
> NodeCmd calls StorageService.effectiveOwnership which seems like it should be definitive
in terms of calculating the number of replicas.  Then NodeCmd.printRing goes through that
and takes each filtered list of datacenters and prints each with replica and node information
via NodeCmd.printDc.
> Hopefully it's just a corner case bug in the reporting itself, but I thought I would
log this in case there was a corner case with the actual ownership during range movements.
 Also the range movements could be a red herring that is just coincidental to this problem.



--
This message was sent by Atlassian JIRA
(v6.1#6144)

Mime
View raw message