>
> The node with IP 94 is leaving. Maybe something wrong happens during
> streaming data. You could use "nodetool netstats" on both nodes to monitor
> if there is any streaming connection stuck.
> Indeed, you could force remove the leaving node by shutting down it
> directly. Then, perform "nodeto
Hi Tim,
The node with IP 94 is leaving. Maybe something wrong happens during
streaming data. You could use "nodetool netstats" on both nodes to monitor
if there is any streaming connection stuck.
Indeed, you could force remove the leaving node by shutting down it
directly. Then, perform "nodetool
>
> "Also, is there any document that explains what all the nodetool
> abbreviations (UN, UL) stand for?"
> --> The documentation is in the command output itself
> Datacenter: datacenter1
> ===
>
> *Status=Up/Down*
> *|/ State=Normal/Leaving/Joining/Moving*-- Address Lo
"Also, is there any document that explains what all the nodetool
abbreviations (UN, UL) stand for?"
--> The documentation is in the command output itself
Datacenter: datacenter1
===
*Status=Up/Down*
*|/ State=Normal/Leaving/Joining/Moving*
-- Address Load Tokens
>
> As I see the state 162.243.109.94 is UL(Up/Leaving) so maybe this is
> causing the problem
OK, that's an interesting observation.How do you fix a node that is an UL
state? What causes this?
Also, is there any document that explains what all the nodetool
abbreviations (UN, UL) stand for?
On
As I see the state 162.243.109.94 is UL(Up/Leaving) so maybe this is causing
the problem.
On Sunday, October 26, 2014 11:57 PM, Tim Dunphy
wrote:
Hey all,
I'm trying to decommission a node.
First I'm getting a status:
[root@beta-new:/usr/local] #nodetool statusNote: Ownership inf
Hey all,
I'm trying to decommission a node.
First I'm getting a status:
[root@beta-new:/usr/local] #nodetool status
Note: Ownership information does not include topology; for complete
information, specify a keyspace
Datacenter: datacenter1
===
Status=Up/Down
|/ State=Normal
