Database Reference
In-Depth Information
KB 66.67% -9223372036854775808
127.0.0.2 rack1 Down Normal 54.82
KB 66.67% -3074457345618258603
127.0.0.3 rack1 Up Normal 71.09
KB 66.67% 3074457345618258602
You can see that node 2 (127.0.0.2) has been down and displayed
with Status as
Down
.
2.
Let's configure a new node and assign it a token value that decreases
the token at 127.0.0.2 by one (i.e., -3074457345618258604). Before
starting the new node, however, let's run a few commands to repair
and remove the dead node:
vivek@vivek-Vostro-3560:~/software/
local-cluster/node1$ bin/nodetool rebuild
vivek@vivek-Vostro-3560:~/software/
local-cluster/node1$ bin/nodetool removenode
fd733376-0cf0-49af-bd0b-79ab526350f8
Here,
fd733376-0cf0-49af-bd0b-79ab526350f8
is the
host ID for node 2. You can fetch the host ID for each node by run-
ning the
nodetool
status command.
3.
Finally, start the new node configured in the previous step and check
the ring status:
vivek@vivek-Vostro-3560:~/software/
local-cluster/node1$ bin/nodetool status
Datacenter: datacenter1
=======================
Status=Up/Down
|/ State=Normal/Leaving/Joining/Moving
-- Address Load Tokens Owns
(effective) Host
ID Rack
UN 127.0.0.4 78.66 KB 256
66.7%
cdcecd4b-ac26-4763-99c4-9f757c2d8074 rack1
UN 127.0.0.1 50.44 KB 1
