sometimes 3-5 times isn't enough. In such cases, shoot for
>> the moon and try 20 assassination attempts in quick succession.
>>
>> 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
ssassination attempts in quick succession.
>>
>> 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 sta
gt; deprecated node, the cosmetic issue will no longer be a concern in any
> system.logs, nodetool describecluster commands, nor nodetool gossipinfo
> output.
>
>
>
>
>
> -Original Message-
> From: Kenneth Brotman [mailto:kenbrot...@yahoo.com.INVALID]
> Sent: Th
: Assassinate fails
Alex,
Did you remove the option JVM_OPTS="$JVM_OPTS
-Dcassandra.replace_address=address_of_dead_node after the node started and
then restart the node again?
Are you sure there isn't a typo in the file?
Ken
-Original Message-
From: Kenneth Brotman [mail
om.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: user@cassandra.
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 keyspa
al 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 Brotman
> wrote:
> >
>
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
> -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
> w
# wait for this to return before moving
> on to the next node.
>
> Restart them all using this method, then 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
should never 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
ait for this to return before moving
> on to the next node.
>
> Restart them all using this method, then 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 su
From: Alain RODRIGUEZ [mailto:arodr...@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 syst
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
omething 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 again!
>
>
>
> *From:* Alex [mailto:m...@aca-o.com]
> *Sent:* Thursday, April 04, 20
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 --
> java.lang
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
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 it
at
ar ./jmxterm.jar
>>>
>>> $>open localhost:7199
>>>
>>> $>bean org.apache.cassandra.net:type=Gossiper
>>>
>>> $>run unsafeAssassinateEndpoint 192.168.1.18
>>>
>>> $>quit
>>>
>>>
>>> Happy de
> > $>quit
> >
> >
> > Happy deleting
> >
> > -Original Message-
> > From: Alex [mailto:m...@aca-o.com]
> > Sent: Wednesday, April 03, 2019 10:42 AM
> > To: user@cassandra.apache.org
> > Subject: Assassinate fails
> >
> &
pril 03, 2019 10:42 AM
To: user@cassandra.apache.org
Subject: Assassinate fails
Hello,
Short story:
- I had to replace a dead node in my cluster
- 1 week after, dead node is still seen as DN by 3 out of 5 nodes
- dead node has null host_id
- assassinate on dead node fails with error
How can I get
.168.1.18
$>quit
Happy deleting
-Original Message-
From: Alex [mailto:m...@aca-o.com]
Sent: Wednesday, April 03, 2019 10:42 AM
To: user@cassandra.apache.org
Subject: Assassinate fails
Hello,
Short story:
- I had to replace a dead node in my cluster
- 1 week after, dead node is still see
Hello,
Short story:
- I had to replace a dead node in my cluster
- 1 week after, dead node is still seen as DN by 3 out of 5 nodes
- dead node has null host_id
- assassinate on dead node fails with error
How can I get rid of this dead node ?
Long story:
I had a 3 nodes cluster (Cassandra 3.9)
23 matches
Mail list logo