Re: Logs appear to contradict themselves during bootstrap steps

2017-01-10 Thread Sotirios Delimanolis
There was no need to assassinate in this case. 'nodetool removenode' worked fine (didn't want to risk losing data). I just don't follow the logic described by the logs. On Friday, January 6, 2017 5:45 PM, Edward Capriolo wrote: On Fri, Jan 6, 2017 at 6:45 PM, Sotirios Delimanolis w

Re: Logs appear to contradict themselves during bootstrap steps

2017-01-06 Thread Edward Capriolo
On Fri, Jan 6, 2017 at 6:45 PM, Sotirios Delimanolis wrote: > I forgot to check nodetool gossipinfo. Still, why does the first check > think that the address exists, but the second doesn't? > > > On Friday, January 6, 2017 1:11 PM, David Berry > wrote: > > > I’ve encountered this previously wher

Re: Logs appear to contradict themselves during bootstrap steps

2017-01-06 Thread Sotirios Delimanolis
I forgot to check nodetool gossipinfo. Still, why does the first check think that the address exists, but the second doesn't? On Friday, January 6, 2017 1:11 PM, David Berry wrote: #yiv4782259727 #yiv4782259727 -- _filtered #yiv4782259727 {panose-1:2 4 5 3 5 4 6 3 2 4;} _filtered #yiv

RE: Logs appear to contradict themselves during bootstrap steps

2017-01-06 Thread David Berry
I’ve encountered this previously where after removing a node, gossip info is retained for 72 hours which doesn’t allow the IP to be reused during that period. You can check how long gossip will retain this information using “nodetool gossipinfo” where the epoch time will be shown with status