[ 
https://issues.apache.org/jira/browse/CASSANDRA-14615?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16565490#comment-16565490
 ] 

Chris Lohfink edited comment on CASSANDRA-14615 at 8/1/18 3:31 PM:
-------------------------------------------------------------------

There was CASSANDRA-8236  that added a delay in announcing its up until native 
and binary are up over CQL.  This state is exposed in {{RPC_READY}} in gossip. 
Its just not what is displayed in nodetool status as Jeremy mentioned there is 
a difference between what the two mean. You can still use {{nodetool 
gossipinfo}} and check {{RPC_READY}} for this information.


was (Author: cnlwsu):
There was CASSANDRA-8236  that added a delay in announcing its up until native 
and binary are up over CQL.  This state is exposed in RPC_READY in gossip. Its 
just not what is displayed in nodetool status as Jeremy mentioned there is a 
difference between what the two mean. You can still use {{nodetool gossipinfp}} 
and check RPC_READY for this information.

> Node status turns to UN although thrift and native transport port are not 
> open to listen
> ----------------------------------------------------------------------------------------
>
>                 Key: CASSANDRA-14615
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-14615
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Core
>            Reporter: Anshu Vajpayee
>            Priority: Critical
>              Labels: startup, startup-time
>
> During startup , Node status turns to UN but not having the thrift and native 
> transport ports open.  It is misleading. 
> As per our understanding UN stands : node is up and running fine and ready to 
> connect from  clients. 
> It would be more appropriate if node shows UN status only when ports are open 
> for client connection. 
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

Reply via email to