sorry for the barrage of questions.... but I'm having = trouble with the nodetool remove phase.=C2=A0

[root@cass= andra01 ~]# 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 -92085= 84805646615844 | head -5

Unrecognized option: -920858480564661584= 4

usage: java org.apache.cassandra.tools.NodeCmd --host <arg> <= command>

=C2=A0-a,--include-all-sstables =C2=A0= includes sstables that are already on the

=C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0most recent version during upgradesstables

=C2=A0-c,--compact =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0print histograms in a more compact format

<= div>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 quo= tes 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, T= im Dunphy <bluethundr@gmail.com> wrote:

Just wondering.. might I be= able to retried the 'lost' intital_token of the node I want to rem= ove by going:

[root@beta-new:~] #nodetool ring | grep 10.10.1.102 | h= ead -1

107.170.175.102 =C2=A0rack1 =C2=A0 =C2=A0 =C2=A0 Down =C2=A0 Normal = =C2=A0123.41 KB =C2=A0 =C2=A0 =C2=A0 32.19% =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0-9208584805646615844

Then

1) place that token in the cassandra.yaml of a new = node with a new IP as =C2=A0-9208584805646615844 -1=C2=A0

2) =C2=A0set auto_bootstrap in the cassandra.yaml
3) once th= e node boots run 'nodetool removetoken -9208584805646615844'
<= div>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,

=C2=A0I have two dead nodes in my ring.=C2= =A0

Status=3DUp/Down

|/ State=3DNormal/Leaving/Joining/Moving

--=C2=A0 Address=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 Load =C2=A0 =C2=A0 = =C2=A0 Tokens=C2=A0 Owns =C2=A0 Host ID =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 Rack<= /p>
DN=C2=A0 10.10.1.102=C2=A0 123.41 KB=C2=A0 256 =C2=A0 =C2=A0 32.2%=C2=A0= ddcafc75-24ed-4c6a-99bb-afe3dd551a9c=C2=A0 rack1

UN=C2=A0 10.10.1.94 =C2=A0 170.81 KB=C2=A0 256 =C2=A0 =C2=A0 35.4%=C2=A0= fd2f76ae-8dcf-4e93-a37f-bf1e9088696e=C2=A0 rack1

DN=C2=A0 10..10.10.64 =C2=A0 ?=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 256 =C2= =A0 =C2=A0 32.5%=C2=A0 f2a48fc7-a362-43f5-9061-4bb3739fdeaf=C2=A0 rack1
=

Unfortunately I am early in my learning curve and failed to p= reserve the initial_token for each of the nodes that were taken out of serv= ice. As things stand now I cannot do a nodetool repair on the main keyspace= because of the dead nodes.=C2=A0

Is there any way to decommission the dead nodes if you no longer have th= eir initial_token values?

Thanks
Tim

--
GPG me!!

gpg --keyserver pool.sks-keyserve= rs.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

--001a11c258dcecdd3404fabe8e44--