cassandra-commits mailing list archives

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

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

Brandon Williams commented on CASSANDRA-9244:
---------------------------------------------

What snitch were you using?  If it's a gossiping snitch, shadow gossip will copy the info,
otherwise it's up to your snitch's config.

> 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