[ https://issues.apache.org/jira/browse/CASSANDRA-7663?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brandon Williams updated CASSANDRA-7663: ---------------------------------------- Attachment: 7663-v2.txt I think it's definitely a Bad Idea to forcibly yank things from Cassandra's classpath, especially since if you do you get this bug, but here's a patch that can tolerate it. > 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-v2.txt, 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)