You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Matt Kapilevich (JIRA)" <ji...@apache.org> on 2013/10/08 22:10:43 UTC
[jira] [Commented] (CASSANDRA-5913) Nodes with no gossip STATUS
shown as "UN" by nodetool:status
[ https://issues.apache.org/jira/browse/CASSANDRA-5913?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13789631#comment-13789631 ]
Matt Kapilevich commented on CASSANDRA-5913:
--------------------------------------------
We're having the same issue. One of our nodes crashed due to bad disk, but it was still marked UP in "nodetool ring".
{code}
54.244.26.215 2b Up Normal 453.39 GB 6.25% 138239711561631250781995934269155835904
{code}
When we run "gossipinfo", here's what we see:
{code}
/54.244.26.215
RELEASE_VERSION:1.2.6.6
RACK:2b
SCHEMA:1f295f0d-e536-324f-8e54-10acb1844f90
DC:us-west-2
INTERNAL_IP:10.89.8.232
SEVERITY:0.0
NET_VERSION:6
HOST_ID:89c15817-de39-4fe5-86f8-5f1cf56e2b17
RPC_ADDRESS:0.0.0.0
{code}
STATUS is not set at all, and SEVERITY is 0.0. We're running 1.2.6
> Nodes with no gossip STATUS shown as "UN" by nodetool:status
> ------------------------------------------------------------
>
> Key: CASSANDRA-5913
> URL: https://issues.apache.org/jira/browse/CASSANDRA-5913
> Project: Cassandra
> Issue Type: Bug
> Components: Core
> Environment: 1.2.8
> Reporter: Chris Burroughs
> Priority: Minor
>
> I have no idea if this is a "valid" situation or a larger problem, but either way nodetool status should not make it look like everything is a-okay.
> From nt:gossipinfo:
> {noformat}
> /64.215.255.182
> RACK:NOP
> NET_VERSION:6
> HOST_ID:4f3b214b-b03e-46eb-8214-5fab2662a06b
> RELEASE_VERSION:1.2.8
> DC:IAD
> INTERNAL_IP:10.15.2.182
> SCHEMA:59adb24e-f3cd-3e02-97f0-5b395827453f
> RPC_ADDRESS:0.0.0.0
> {noformat}
> {noformat}
> $ ./bin/nt.sh status | grep -i 4055109d-800d-4743-8efa-4ecfff883463
> UN 64.215.255.182 63.84 GB 256 2.5% 4055109d-800d-4743-8efa-4ecfff883463 NOP
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.1#6144)