[
https://issues.apache.org/jira/browse/CASSANDRA-7663?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14083258#comment-14083258
]
Richard Low commented on CASSANDRA-7663:
----------------------------------------
Actually there's a potential problem with this. It now requires that the yaml
is still present, whereas before this patch the yaml was only needed on
startup. Depending on how people deploy updated yamls, the old yaml may not be
there. In that case, it would throw AssertionError and bad things will happen
in gossip. Maybe it could fall back on the original behaviour if the yaml can't
be read?
> Removing a seed causes previously removed seeds to reappear
> -----------------------------------------------------------
>
> Key: CASSANDRA-7663
> URL: https://issues.apache.org/jira/browse/CASSANDRA-7663
> Project: Cassandra
> Issue Type: Bug
> Reporter: Richard Low
> Assignee: Brandon Williams
> Fix For: 1.2.19, 2.0.10, 2.1.0
>
> Attachments: 7663.txt
>
>
> When you remove a seed from a cluster, Gossiper.removeEndpoint ensures it is
> removed from the seed list. However, it also resets the seed list to be the
> original list, which would bring back any previously removed seeds. What is
> the reasoning for having the call to buildSeedsList()? If it wasn’t there
> then I think the problem would be solved.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
