Re: Cannot replace_address /10.xx.xx.xx because it doesn't exist in gossip

2019-03-14 Thread Jeff Jirsa
Two things that wouldn't be a bug: You could have run removenode You could have run assassinate Also could be some new bug, but that's much less likely. On Thu, Mar 14, 2019 at 2:50 PM Fd Habash wrote: > I have a node which I know for certain was a cluster member last week. It > showed in

Cannot replace_address /10.xx.xx.xx because it doesn't exist in gossip

2019-03-14 Thread Fd Habash
I have a node which I know for certain was a cluster member last week. It showed in nodetool status as DN. When I attempted to replace it today, I got this message ERROR [main] 2019-03-14 14:40:49,208 CassandraDaemon.java:654 - Exception encountered during startup java.lang.RuntimeException: