[
https://issues.apache.org/jira/browse/CASSANDRA-5913?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13789782#comment-13789782
]
Brandon Williams commented on CASSANDRA-5913:
---------------------------------------------
What especially doesn't make sense here is that, as you say, everything is
reaching deep into the gossiper, and getLiveMembers is essentially controlled
by notifications from the FailureDetector. Nothing has changed in the FD in a
long time.
> 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)
