cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rick Branson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-9244) replace_address is not topology-aware
Date Sat, 25 Apr 2015 22:26:38 GMT

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

Rick Branson commented on CASSANDRA-9244:
-----------------------------------------

GossipingPropertyFileSnitch. The scenario is say you have NTS with RF=3, 10 racks A-J, and
range R1, which is spread across nodes A1, C1, and E1 in racks A, C, and E respectively. If
you replace_address C1 with node E2, it will cause range R1 to shift to A1, E2, and some node
in neither A nor E racks. A similar range change is achieved if you were to bootstrap with
tokens-1, but the shifts will work properly in that case.

> replace_address is not topology-aware
> -------------------------------------
>
>                 Key: CASSANDRA-9244
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-9244
>             Project: Cassandra
>          Issue Type: Bug
>         Environment: 2.0.12
>            Reporter: Rick Branson
>
> Replaced a node with one in another rack (using replace_address) and it caused improper
distribution after the bootstrap was finished. It looks like the ranges for the streams are
not created in a way that is topology-aware. This should probably either be prevented, or
ideally, would work properly. The use case is migrating several nodes from one rack to another.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message