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 2018/05/15 18:41:00 UTC

[jira] [Commented] (CASSANDRA-14073) Prevent replacement nodes from skipping bootstrapping without allow_unsafe_replace:true

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

Blake Eggleston commented on CASSANDRA-14073:
---------------------------------------------

Seems like this is also an issue in 3.0 and trunk. Could you provide patches for them as well?

> Prevent replacement nodes from skipping bootstrapping without allow_unsafe_replace:true
> ---------------------------------------------------------------------------------------
>
>                 Key: CASSANDRA-14073
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-14073
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Configuration
>            Reporter: Vincent White
>            Assignee: Vincent White
>            Priority: Minor
>              Labels: bootstrap, patch
>             Fix For: 3.11.x
>
>
> I've noticed that when replacing a node with replace_address it can skip bootstrapping if it is listed in its own seed list. This probably shouldn't be allowed without the allow_unsafe_replace option set to true as is required when using auto_bootstrap: false in combination with replace_address. Patch [here|https://github.com/vincewhite/cassandra/commits/replace_address_seed_list] and an attempt at a dtest [here|https://github.com/vincewhite/cassandra-dtest/commits/unsafe_replace]. 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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