You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Brandon Williams (Jira)" <ji...@apache.org> on 2022/09/12 13:02:00 UTC
[jira] [Updated] (CASSANDRA-17883) Node will not get schema updates if it replaces a removed node with the same address
[ https://issues.apache.org/jira/browse/CASSANDRA-17883?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brandon Williams updated CASSANDRA-17883:
-----------------------------------------
Bug Category: Parent values: Correctness(12982)Level 1 values: Consistency(12989)
Complexity: Normal
Discovered By: User Report
Fix Version/s: 3.0.x
3.11.x
4.0.x
4.x
Severity: Normal
Status: Open (was: Triage Needed)
/cc [~bdeggleston]
> 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, 4.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-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org