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

[jira] [Updated] (CASSANDRA-16278) Bootstrapping nodes can become unreplaceable

     [ https://issues.apache.org/jira/browse/CASSANDRA-16278?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Blake Eggleston updated CASSANDRA-16278:
----------------------------------------
    Test and Documentation Plan: circle
                         Status: Patch Available  (was: Open)

| [3.0|https://github.com/bdeggleston/cassandra/tree/16278-3.0] | [circle|https://app.circleci.com/pipelines/github/bdeggleston/cassandra?branch=16278-3.0]|
| [3.11|https://github.com/bdeggleston/cassandra/tree/16278-3.11] | [circle|https://app.circleci.com/pipelines/github/bdeggleston/cassandra?branch=16278-3.11]|
| [trunk|https://github.com/bdeggleston/cassandra/tree/16278-trunk] | [circle|https://app.circleci.com/pipelines/github/bdeggleston/cassandra?branch=16278-trunk]|


> Bootstrapping nodes can become unreplaceable
> --------------------------------------------
>
>                 Key: CASSANDRA-16278
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-16278
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Cluster/Gossip
>            Reporter: Blake Eggleston
>            Assignee: Blake Eggleston
>            Priority: Normal
>
> Bootstrapping nodes (including replacements) don't gossip their tokens until after they've received their schema. If the node experiences a failure before gossiping tokens, it causes the same problem CASSNDRA-15335 fixed for normal nodes - they cannot be replaced without gossiped tokens. Including tokens in the initial gossip round prevents nodes from getting into this state, although we still have to wait for the schema when the node is configured to allocate tokens for a keyspace.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org