[
https://issues.apache.org/jira/browse/CASSANDRA-19719?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Capwell updated CASSANDRA-19719:
--------------------------------------
Bug Category: Parent values: Correctness(12982)Level 1 values:
Unrecoverable Corruption / Loss(13161)
Complexity: Low Hanging Fruit
Discovered By: Fuzz Test
Fix Version/s: NA
Severity: Critical
Assignee: David Capwell
Status: Open (was: Triage Needed)
> CEP-15: (Accord) When nodes are removed from a cluster, need to update
> topology tracking to avoid being blocked
> ---------------------------------------------------------------------------------------------------------------
>
> Key: CASSANDRA-19719
> URL: https://issues.apache.org/jira/browse/CASSANDRA-19719
> Project: Cassandra
> Issue Type: Bug
> Components: Accord
> Reporter: David Capwell
> Assignee: David Capwell
> Priority: Normal
> Fix For: NA
>
>
> When doing a host replacement or decom nodes will leave the cluster and won't
> ever come back, this can put accord's topology sync logic into a bad state as
> its going to wait forever for those nodes to acknowledge the epoch or parts
> of the ranges.
--
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
