incubator-cassandra-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Tim Dunphy <bluethu...@gmail.com>
Subject Re: decommission dead node without token
Date Sun, 01 Jun 2014 04:41:58 GMT
>
> backslash it  \-9485547484
> just guessing.


Oh, worth a shot! But I'm heading to bed now. I'll try again with this
tomorrow.

cya

Tim


On Sun, Jun 1, 2014 at 12:39 AM, Spencer Brown <lilspenny@gmail.com> wrote:

> backslash it  \-9485547484
> just guessing.
>
>
> On Sun, Jun 1, 2014 at 12:31 AM, Tim Dunphy <bluethundr@gmail.com> wrote:
>
>> nodetool -host 10.10.1.68 removetoken -9208584805646615844
>>
>>
>> I still get a unix usage message with this syntax, yo. Just a theory
>> dude, but I think that the negative sign is confusing bash.
>>
>> But yeah definitely fixing posts is the priority. Then maybe we can
>> tackle my cassandra woes. And then move onto improving the font.  Mainly
>> cassandra is an issue in that I can't do a repair on the database unless
>> all nodes are present with none down. I definitely think there's a way out
>> of this jam. I hope that the list has some input here.
>>
>>  But definitely don't worry about JF until you're caught up with work. I
>> want to see you keep this job going as much as you can. Like I do with mine
>> at NBCU! :)
>>
>> on fixing posting or nodes?  I don't think posting fix should be too
>>> hard.  I'm mainly just late with my primary job in fixing something which
>>> should be easy.  It's an AJAX sort of thing.  Have you dealt with that...
>>>  it's hard.  It means Asynchronous Javascript and XML.  And there's an HTML
>>> element too.  And in this case there is some JQuery.  And when you combine
>>> all that it becomes a pain in the ass.
>>
>>
>> Never really dealt with AJAX. Always meant to get into it tho. I hear it
>> can be powerful! But definitely good luck with that! And I hope you can
>> indeed get to do some JF stuff this weekend. But don't stress about it if
>> you're stuck with work.
>>
>> Tim
>>
>>
>>
>>
>>
>> On Sun, Jun 1, 2014 at 12:21 AM, Spencer Brown <lilspenny@gmail.com>
>> wrote:
>>
>>> nodetool -host 10.10.1.68 removetoken -9208584805646615844
>>>
>>>
>>> On Sun, Jun 1, 2014 at 12:17 AM, Tim Dunphy <bluethundr@gmail.com>
>>> wrote:
>>>
>>>> sorry for the barrage of questions.... but I'm having trouble with the
>>>> nodetool remove phase.
>>>>
>>>> [root@cassandra01 ~]# nodetool removetoken -h 10.10.1.68
>>>> -9208584805646615844
>>>>
>>>> Gives me a unix usage message. As in:
>>>>
>>>> [root@cassandra01 ~]# nodetool removetoken -h 107.170.178.68
>>>> -9208584805646615844 | head -5
>>>> Unrecognized option: -9208584805646615844
>>>> usage: java org.apache.cassandra.tools.NodeCmd --host <arg> <command>
>>>>
>>>>  -a,--include-all-sstables   includes sstables that are already on the
>>>>                              most recent version during upgradesstables
>>>>  -c,--compact                print histograms in a more compact format
>>>>
>>>> I think the problem is that the bash environment is getting confused by
>>>> the minus sign in front of the token. But that is the token and the minus
>>>> sign is integral to it. I've even tried quoting it with both single quotes
>>>> and double quotes to no avail. I still get the same usage message.
>>>>
>>>> Can someone please help with the right syntax here?
>>>>
>>>> Thanks
>>>> Tim
>>>>
>>>>
>>>> On Sun, Jun 1, 2014 at 12:01 AM, Tim Dunphy <bluethundr@gmail.com>
>>>> wrote:
>>>>
>>>>> Just wondering.. might I be able to retried the 'lost' intital_token
>>>>> of the node I want to remove by going:
>>>>>
>>>>> [root@beta-new:~] #nodetool ring | grep 10.10.1.102 | head -1
>>>>> 107.170.175.102  rack1       Down   Normal  123.41 KB       32.19%
>>>>>          -9208584805646615844
>>>>>
>>>>> Then
>>>>>
>>>>> 1) place that token in the cassandra.yaml of a new node with a new IP
>>>>> as  -9208584805646615844 -1
>>>>> 2)  set auto_bootstrap in the cassandra.yaml
>>>>> 3) once the node boots run 'nodetool removetoken -9208584805646615844'
>>>>> 4) run nodetool cleanup
>>>>>
>>>>> Would this be the way to get out of this bind? Just want to be sure I
>>>>> understand the process.
>>>>>
>>>>> Thanks
>>>>> Tim
>>>>>
>>>>>
>>>>> On Sat, May 31, 2014 at 10:38 PM, Tim Dunphy <bluethundr@gmail.com>
>>>>> wrote:
>>>>>
>>>>>> hey guys,
>>>>>>
>>>>>>  I have two dead nodes in my ring.
>>>>>>
>>>>>>  Status=Up/Down
>>>>>>
>>>>>> |/ State=Normal/Leaving/Joining/Moving
>>>>>>
>>>>>> --  Address          Load       Tokens  Owns   Host ID
>>>>>>                 Rack
>>>>>>
>>>>>> DN  10.10.1.102  123.41 KB  256     32.2%
>>>>>> ddcafc75-24ed-4c6a-99bb-afe3dd551a9c  rack1
>>>>>>
>>>>>> UN  10.10.1.94   170.81 KB  256     35.4%
>>>>>> fd2f76ae-8dcf-4e93-a37f-bf1e9088696e  rack1
>>>>>>
>>>>>> DN  10..10.10.64   ?          256     32.5%
>>>>>> f2a48fc7-a362-43f5-9061-4bb3739fdeaf  rack1
>>>>>>
>>>>>>
>>>>>> Unfortunately I am early in my learning curve and failed to preserve
>>>>>> the initial_token for each of the nodes that were taken out of service.
As
>>>>>> things stand now I cannot do a nodetool repair on the main keyspace
because
>>>>>> of the dead nodes.
>>>>>>
>>>>>> Is there any way to decommission the dead nodes if you no longer
have
>>>>>> their initial_token values?
>>>>>>
>>>>>>
>>>>>> Thanks
>>>>>>
>>>>>> Tim
>>>>>>
>>>>>> --
>>>>>> GPG me!!
>>>>>>
>>>>>> gpg --keyserver pool.sks-keyservers.net --recv-keys F186197B
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> GPG me!!
>>>>>
>>>>> gpg --keyserver pool.sks-keyservers.net --recv-keys F186197B
>>>>>
>>>>>
>>>>
>>>>
>>>> --
>>>> GPG me!!
>>>>
>>>> gpg --keyserver pool.sks-keyservers.net --recv-keys F186197B
>>>>
>>>>
>>>
>>
>>
>> --
>> GPG me!!
>>
>> gpg --keyserver pool.sks-keyservers.net --recv-keys F186197B
>>
>>
>


-- 
GPG me!!

gpg --keyserver pool.sks-keyservers.net --recv-keys F186197B

Mime
View raw message