[
https://issues.apache.org/jira/browse/CASSANDRA-9180?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14538143#comment-14538143
]
Ariel Weisberg commented on CASSANDRA-9180:
-------------------------------------------
[~brandon.williams] can you update [kitchen sink
doc|https://docs.google.com/document/d/1kccPqxEAoYQpT0gXnp20MYQUDmjOrakAeQhf6vkqjGo/edit?pli=1#heading=h.zd5nw0kl2ypi]
with a description of any inconvenient windows you can think of to kill a node
during bootstrap? We can have the harness kill nodes based on time or based on
log messages.
Or maybe that is the wrong way to go about addressing bugs stemming from stale
or broken state related to cluster membership and connectivity. Just thinking
of how we can make it work more consistently.
> Failed bootstrap/replace attempts persist entries in system.peers
> -----------------------------------------------------------------
>
> Key: CASSANDRA-9180
> URL: https://issues.apache.org/jira/browse/CASSANDRA-9180
> Project: Cassandra
> Issue Type: Bug
> Components: Core
> Reporter: Brandon Williams
> Assignee: Brandon Williams
> Fix For: 2.0.15, 2.1.5
>
> Attachments: 9081.txt
>
>
> In working on CASSANDRA-8336, I discovered vanilla C* has this problem. Just
> start a bootstrap or replace and kill it during the ring info gathering
> phase. System.peers, the gift that keeps on giving.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
