>
> 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 wrote:
> backslash it \-9485547484
> just guessing.
>
>
> On Sun, Jun 1, 2014 at 12:31 AM, Tim Dunphy wro
backslash it \-9485547484
just guessing.
On Sun, Jun 1, 2014 at 12:31 AM, Tim Dunphy 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.
>
>
>
> 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 m
nodetool -host 10.10.1.68 removetoken -9208584805646615844
On Sun, Jun 1, 2014 at 12:17 AM, Tim Dunphy 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
>
>
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 | he
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 c
Ouch. I really don't think so.
On Sat, May 31, 2014 at 10:38 PM, Tim Dunphy 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 1
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
>
> I think the "deaf" thing is just the ending of the host ID in hexadecimal.
> It's an extraordinary coincidence that it ends with DEAF :D
Hah.. yeah that thought did cross my mind. :)
On Sat, May 31, 2014 at 1:35 PM, DuyHai Doan wrote:
> I think the "deaf" thing is just the ending of the
I think the "deaf" thing is just the ending of the host ID in hexadecimal.
It's an extraordinary coincidence that it ends with DEAF :D
On Sat, May 31, 2014 at 6:38 PM, Tim Dunphy wrote:
> I didn't realize cassandra nodes could develop hearing problems. :)
>
>
> But I have a dead node in my clus
I didn't realize cassandra nodes could develop hearing problems. :)
But I have a dead node in my cluster I would like to get rid of.
[root@beta:~] #nodetool status
Datacenter: datacenter1
===
Status=Up/Down
|/ State=Normal/Leaving/Joining/Moving
-- Address Load
11 matches
Mail list logo