[
https://issues.apache.org/jira/browse/CASSANDRA-5913?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13776384#comment-13776384
]
Jeremy Hanna commented on CASSANDRA-5913:
-----------------------------------------
Another case where there was no gossip STATUS for node X across the cluster
except for on node X. In that case there was a recently bootstrapped node and
it couldn't see node X in either nodetool describering nor in nodetool status
(1.2.6). It could be seen in nodetool status in the rest of the cluster
however. Anyway, so restarting node X refreshed the gossip information and
restored the STATUS part - as well as put it in the describering and nodetool
status output.
> 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
