Re: Assassinate fails

2019-08-29 Thread Alain RODRIGUEZ
> What we are trying to do is to create a flood of messages requesting all >> nodes completely forget there used to be an entry within the gossip state >> for the given IP address. If each node can prune its own gossip state and >> broadcast that to the rest of the nodes,

Re: Assassinate fails

2019-08-16 Thread Alex
nodes completely forget there used to be an entry within the gossip state >> for the given IP address. If each node can prune its own gossip state and >> broadcast that to the rest of the nodes, we should eliminate any race >> conditions that may exist where at least one nod

Re: Assassinate fails

2019-04-05 Thread Alain RODRIGUEZ
cluster commands, nor nodetool gossipinfo > output. > > > > > > -----Original Message----- > From: Kenneth Brotman [mailto:kenbrot...@yahoo.com.INVALID] > Sent: Thursday, April 04, 2019 10:40 AM > To: user@cassandra.apache.org > Subject: RE: Assassinate fails &

RE: Assassinate fails

2019-04-04 Thread Kenneth Brotman
nbrot...@yahoo.com.INVALID] Sent: Thursday, April 04, 2019 10:31 AM To: user@cassandra.apache.org Subject: RE: Assassinate fails I see; system_auth is a separate keyspace. -Original Message- From: Jon Haddad [mailto:j...@jonhaddad.com] Sent: Thursday, April 04, 2019 10:17 AM To:

RE: Assassinate fails

2019-04-04 Thread Kenneth Brotman
VALID] Sent: Thursday, April 04, 2019 10:31 AM To: user@cassandra.apache.org Subject: RE: Assassinate fails I see; system_auth is a separate keyspace. -Original Message- From: Jon Haddad [mailto:j...@jonhaddad.com] Sent: Thursday, April 04, 2019 10:17 AM To: user@cassandra.apach

RE: Assassinate fails

2019-04-04 Thread Kenneth Brotman
I see; system_auth is a separate keyspace. -Original Message- From: Jon Haddad [mailto:j...@jonhaddad.com] Sent: Thursday, April 04, 2019 10:17 AM To: user@cassandra.apache.org Subject: Re: Assassinate fails No, it can't. As Alain (and I) have said, since the system keyspace

Re: Assassinate fails

2019-04-04 Thread Jon Haddad
> From: Jon Haddad [mailto:j...@jonhaddad.com] > Sent: Thursday, April 04, 2019 9:52 AM > To: user@cassandra.apache.org > Subject: Re: Assassinate fails > > System != system_auth. > > On Thu, Apr 4, 2019 at 9:43 AM Kenneth Brotman > wrote: > > > > From Ma

RE: Assassinate fails

2019-04-04 Thread Kenneth Brotman
Right, could be similar issue, same type of fix though. -Original Message- From: Jon Haddad [mailto:j...@jonhaddad.com] Sent: Thursday, April 04, 2019 9:52 AM To: user@cassandra.apache.org Subject: Re: Assassinate fails System != system_auth. On Thu, Apr 4, 2019 at 9:43 AM Kenneth

Re: Assassinate fails

2019-04-04 Thread Jon Haddad
-Original Message- > From: Jon Haddad [mailto:j...@jonhaddad.com] > Sent: Thursday, April 04, 2019 9:21 AM > To: user@cassandra.apache.org > Subject: Re: Assassinate fails > > Ken, > > Alain is right about the system tables. What you're describing only > works on non-loc

Re: Assassinate fails

2019-04-04 Thread Alex
run nodetool status again and see if > it is listed. > > Once other thing, I recall you said something about having to terminate a > node and then replace it. Make sure that whichever node you did the -Dreplace > flag on, does not still have it set when you

RE: Assassinate fails

2019-04-04 Thread Kenneth Brotman
ver use the default cassandra user. -Original Message- From: Jon Haddad [mailto:j...@jonhaddad.com] Sent: Thursday, April 04, 2019 9:21 AM To: user@cassandra.apache.org Subject: Re: Assassinate fails Ken, Alain is right about the system tables. What you're describing only works on

Re: Assassinate fails

2019-04-04 Thread Alex
nodetool status again and see if > it is listed. > > Once other thing, I recall you said something about having to terminate a > node and then replace it. Make sure that whichever node you did the -Dreplace > flag on, does not still have it set when you start cassandra on it ag

Re: Assassinate fails

2019-04-04 Thread Jon Haddad
...@gmail.com] > Sent: Thursday, April 04, 2019 8:46 AM > To: user cassandra.apache.org > Subject: Re: Assassinate fails > > > > Hi Alex, > > > > About previous advices: > > > > You might have inconsistent data in your system tables. Try setting the > c

RE: Assassinate fails

2019-04-04 Thread Kenneth Brotman
The trick below I got from the book Mastering Cassandra. You have to set the consistency to ALL for it to work. I thought you guys knew that one. From: Alain RODRIGUEZ [mailto:arodr...@gmail.com] Sent: Thursday, April 04, 2019 8:46 AM To: user cassandra.apache.org Subject: Re: Assassinate

Re: Assassinate fails

2019-04-04 Thread Alain RODRIGUEZ
u did the > –Dreplace flag on, does not still have it set when you start cassandra on > it again! > > > > *From:* Alex [mailto:m...@aca-o.com] > *Sent:* Thursday, April 04, 2019 4:58 AM > *To:* user@cassandra.apache.org > *Subject:* Re: Assassinate fails > > >

Re: Assassinate fails

2019-04-04 Thread Jeff Jirsa
t; Sent: Thursday, April 04, 2019 4:58 AM > To: user@cassandra.apache.org > Subject: Re: Assassinate fails > > Hi Anthony, > > Thanks for your help. > > I tried to run multiple times in quick succession but it fails with : > > -- StackTrace -

RE: Assassinate fails

2019-04-04 Thread Nick Hatfield
again! From: Alex [mailto:m...@aca-o.com] Sent: Thursday, April 04, 2019 4:58 AM To: user@cassandra.apache.org Subject: Re: Assassinate fails Hi Anthony, Thanks for your help. I tried to run multiple times in quick succession but it fails with : -- StackTrace -- java.lang.RuntimeException: En

RE: Assassinate fails

2019-04-04 Thread Kenneth Brotman
Subject: Re: Assassinate fails Hi Anthony, Thanks for your help. I tried to run multiple times in quick succession but it fails with : -- StackTrace -- java.lang.RuntimeException: Endpoint still alive: /192.168.1.18 generation changed while trying to assassinate

Re: Assassinate fails

2019-04-04 Thread Alex
Hi Anthony, Thanks for your help. I tried to run multiple times in quick succession but it fails with : -- StackTrace -- java.lang.RuntimeException: Endpoint still alive: /192.168.1.18 generation changed while trying to assassinate it at

Re: Assassinate fails

2019-04-03 Thread Anthony Grasso
Hi Alex, We wrote a blog post on this topic late last year: http://thelastpickle.com/blog/2018/09/18/assassinate.html. In short, you will need to run the assassinate command on each node simultaneously a number of times in quick succession. This will generate a number of messages requesting all

Re: Assassinate fails

2019-04-03 Thread Alex
Same result it seems: Welcome to JMX terminal. Type "help" for available commands. $>open localhost:7199 #Connection to localhost:7199 is opened $>bean org.apache.cassandra.net:type=Gossiper #bean is set to org.apache.cassandra.net:type=Gossiper $>run unsafeAssassinateEndpoint 192.168.1.18

RE: Assassinate fails

2019-04-03 Thread Nick Hatfield
Run assassinate the old way. I works very well... wget -q -O jmxterm.jar http://downloads.sourceforge.net/cyclops-group/jmxterm-1.0-alpha-4-uber.jar java -jar ./jmxterm.jar $>open localhost:7199 $>bean org.apache.cassandra.net:type=Gossiper $>run unsafeAssassinateEndpoint 192.168.1.18