[
https://issues.apache.org/jira/browse/CASSANDRA-12344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17928805#comment-17928805
]
Paulo Motta commented on CASSANDRA-12344:
-----------------------------------------
[~samt] is this handled by CASSANDRA-18330 ?
> Forward writes to replacement node with same address during replace
> -------------------------------------------------------------------
>
> Key: CASSANDRA-12344
> URL: https://issues.apache.org/jira/browse/CASSANDRA-12344
> Project: Apache Cassandra
> Issue Type: Improvement
> Components: Cluster/Membership, Consistency/Bootstrap and
> Decommission, Legacy/Distributed Metadata
> Reporter: Paulo Motta
> Assignee: Paulo Motta
> Priority: Normal
> Fix For: 5.x
>
>
> On CASSANDRA-8523 it was added support to forwarding writes to a replacement
> node via a new gossip state {{BOOTSTRAPPING_REPLACE}}.
> Currently this is limited to replacement nodes with a different address of
> the original node, because if a replacement node with the same address of a
> normal endpoint joins gossip with a non-dead state, it will become alive in
> the Failure Detector and reads will be forwarded to it before the node is
> ready to serve reads.
> This ticket is to add support to forwarding writes to replacement nodes with
> the same IP address as the original node.
> The initial idea is to allow marking a node as unavailable for reads on
> {{TokenMetadata}}, what will allow the replacement node with the same IP join
> gossip without having reads forwarded to it. This will be enabled by
> CASSANDRA-11559.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
