cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Brandon Williams (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-7663) Removing a seed causes previously removed seeds to reappear
Date Thu, 31 Jul 2014 23:47:38 GMT

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

Brandon Williams commented on CASSANDRA-7663:
---------------------------------------------

bq.  If you're using SimpleSeedProvider that means the old seed is in your yaml and would
come back with a restart anyway.

Actually I take that back, it looks like SSP itself is caching the seeds in the yaml forever,
which is probably wrong.

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

Mime
View raw message