You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Josh McKenzie (Jira)" <ji...@apache.org> on 2022/09/15 17:45:00 UTC

[jira] [Commented] (CASSANDRA-17896) Failed replacements due to "Cannot replace token xxx which does not exist"

    [ https://issues.apache.org/jira/browse/CASSANDRA-17896?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17605466#comment-17605466 ] 

Josh McKenzie commented on CASSANDRA-17896:
-------------------------------------------

||Item|Link||
|PR|[link|https://github.com/apache/cassandra/pull/1857]|
|JDK8 CI|[link|https://app.circleci.com/pipelines/github/josh-mckenzie/cassandra/297/workflows/2db90a6e-da0d-4be4-9bd1-7463daae228f]|
|JDK11 CI|[link|https://app.circleci.com/pipelines/github/josh-mckenzie/cassandra/297/workflows/01169e19-2409-4302-ad3b-d9722de34bfc]|

> Failed replacements due to "Cannot replace token xxx which does not exist"
> --------------------------------------------------------------------------
>
>                 Key: CASSANDRA-17896
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-17896
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Consistency/Streaming
>            Reporter: Josh McKenzie
>            Assignee: Josh McKenzie
>            Priority: Normal
>             Fix For: 4.x
>
>
> Host replacements require host ID and token, however reporting of this info is typically blocked when the “status” field is missing. We should expose a system env (-D) param to advanced operators to have the ability to specify the replace_addresses_token to be used during host replacement in cases where Gossip gets into a bad state.
> Given this is inherently an unsafe / high risk manual intervention, we want to avoid promoting this to being a config param however Gossip quite often contorts into problematic split-brain states like this and having the ability to manually override things helps unstick host replacements that go straddled. Should update NEWS.txt at the very least and consider documentation as well
> This is an interim solution that'll be obviated by CEP-21, but is still useful on existing clusters.



--
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