[
https://issues.apache.org/jira/browse/CASSANDRA-5913?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13746520#comment-13746520
]
Chris Burroughs commented on CASSANDRA-5913:
--------------------------------------------
Sorry, trying to write up separate discrete tickets instead of one giant
"CASSANDRA AND I HAD A BAD MORNING". It was from a replace_node on a down node
that failed as in CASSANDRA-5914
> 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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
