Apparently this was reported back in May:
https://issues.apache.org/jira/browse/CASSANDRA-9510
- Jeff
From: Dikang Gu
Reply-To: "user@cassandra.apache.org"
Date: Friday, September 25, 2015 at 11:31 AM
To: cassandra
Subject: Re: Unable to remove dead node from cluster.
The NPE t
es). If this is the case, please reply so that you and I can submit a
>>> Jira and compare our stack traces and we can find the underlying root cause
>>> of this together.
>>>
>>> - Jeff
>>>
>>> From: Dikang Gu
>>> Reply-To: "
are our stack traces and we can find the underlying root cause
>> of this together.
>>
>> - Jeff
>>
>> From: Dikang Gu
>> Reply-To: "user@cassandra.apache.org"
>> Date: Thursday, September 24, 2015 at 9:10 PM
>> To: cassandra
>>
>> Subj
that you’re not including in the
>> ‘nodetool status’ output?
>>
>>
>> From: Dikang Gu
>> Reply-To: "user@cassandra.apache.org"
>> Date: Tuesday, September 22, 2015 at 10:09 PM
>> To: cassandra
>> Cc: "d...@cassandra.apache.org"
To: cassandra
Subject: Re: Unable to remove dead node from cluster.
@Jeff, I just use jmx connect to one node, run the unsafeAssainateEndpoint, and
pass in the "10.210.165.55" ip address.
Yes, we have hundreds of other nodes in the nodetool status output as well.
On Tue, Sep 22, 2015 at 11
mber 22, 2015 at 10:09 PM
> To: cassandra
> Cc: "d...@cassandra.apache.org"
> Subject: Re: Unable to remove dead node from cluster.
>
> ping.
>
> On Mon, Sep 21, 2015 at 11:51 AM, Dikang Gu wrote:
>
>> I have tried all of them, neither of them worked.
>>
r 22, 2015 at 10:09 PM
To: cassandra
Cc: "d...@cassandra.apache.org"
Subject: Re: Unable to remove dead node from cluster.
ping.
On Mon, Sep 21, 2015 at 11:51 AM, Dikang Gu wrote:
I have tried all of them, neither of them worked.
1. decommission: the host had hardware issue, and I c
ping.
On Mon, Sep 21, 2015 at 11:51 AM, Dikang Gu wrote:
> I have tried all of them, neither of them worked.
> 1. decommission: the host had hardware issue, and I can not connect to it.
> 2. remove, there is not HostID, so the removenode did not work.
> 3. unsafeAssassinateEndpoint, it will thro
I have tried all of them, neither of them worked.
1. decommission: the host had hardware issue, and I can not connect to it.
2. remove, there is not HostID, so the removenode did not work.
3. unsafeAssassinateEndpoint, it will throw NPE as I pasted before, can we
fix it?
Thanks
Dikang.
On Mon, Se
Order is decommission, remove, assassinate.
Which have you tried?
On Sep 21, 2015 10:47 AM, "Dikang Gu" wrote:
> Hi there,
>
> I have a dead node in our cluster, which is a wired state right now, and
> can not be removed from cluster.
>
> The nodestatus shows:
> Datacenter: DC1
> ===
Hi there,
I have a dead node in our cluster, which is a wired state right now, and
can not be removed from cluster.
The nodestatus shows:
Datacenter: DC1
===
Status=Up/Down
|/ State=Normal/Leaving/Joining/Moving
-- Address Load Tokens OwnsHost ID
11 matches
Mail list logo
