cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Paulo Motta (JIRA)" <j...@apache.org>
Subject [jira] [Assigned] (CASSANDRA-9244) replace_address is not topology-aware
Date Thu, 30 Mar 2017 21:23:42 GMT

     [ https://issues.apache.org/jira/browse/CASSANDRA-9244?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Paulo Motta reassigned CASSANDRA-9244:
--------------------------------------

         Assignee:     (was: Paulo Motta)
    Reproduced In: 3.1, 3.0.2, 2.1.12, 2.0.17  (was: 2.0.17, 2.1.12, 3.0.2, 3.1)

> 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
>             Fix For: 2.1.x, 2.2.x, 3.0.x, 3.11.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.15#6346)

Mime
View raw message