[
https://issues.apache.org/jira/browse/CASSANDRA-9244?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Paulo Motta updated CASSANDRA-9244:
-----------------------------------
Reproduced In: 3.1, 3.0.2, 2.1.12, 2.0.17
Fix Version/s: 3.x
3.0.x
2.2.x
2.1.x
> replace_address is not topology-aware
> -------------------------------------
>
> Key: CASSANDRA-9244
> URL: https://issues.apache.org/jira/browse/CASSANDRA-9244
> Project: Cassandra
> Issue Type: Bug
> Components: Distributed Metadata, Streaming and Messaging
> Environment: 2.0.12
> Reporter: Rick Branson
> Assignee: Paulo Motta
> Fix For: 2.1.x, 2.2.x, 3.0.x, 3.x
>
>
> 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)
