[ https://issues.apache.org/jira/browse/CASSANDRA-17883 ]
Jeff Jirsa deleted comment on CASSANDRA-17883:
----------------------------------------
was (Author: jjirsa):
When you stream a host with an existing IP (and same token), you don't get ANY
writes during bootstrap stream (you get the stream, but you wont get any other
writes).
IIRC, it's related to how the write logic would increment `blockFor`, but the
coordinator can't tell which version of the IP acks a write (old one or new
one), so it cant actually implement the extra write for the pending range.
> Node will not get schema updates if it replaces a removed node with the same
> address
> ------------------------------------------------------------------------------------
>
> Key: CASSANDRA-17883
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17883
> Project: Cassandra
> Issue Type: Bug
> Components: Legacy/Distributed Metadata
> Reporter: Jacek Lewandowski
> Priority: Normal
> Fix For: 3.0.x, 3.11.x, 4.0.x, 5.x
>
>
> If a node is removed and then a node with the same address is added, it is
> ignored by migration coordinator - that is, when that node fails to push the
> schema change, the other nodes will not be able pull it later during periodic
> update.
> Such situation will last until the other nodes gets restarted.
> This is caused by permanently adding the address of the node being removed to
> the ignore list in migration coordinator.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
