cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Brandon Williams (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-8791) 'nodetool status' reports nodes in undocumented '?' state
Date Mon, 30 Mar 2015 13:48:53 GMT

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

Brandon Williams commented on CASSANDRA-8791:
---------------------------------------------

Honestly, parsing nodetool output is a bad idea in general.  We make no guarantees we won't
make cosmetic changes to that, even in a minor.  Instead you need to use JMX programmatically
yourself because that won't change.

> 'nodetool status' reports nodes in undocumented '?' state
> ---------------------------------------------------------
>
>                 Key: CASSANDRA-8791
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-8791
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: Stuart Bishop
>            Priority: Minor
>             Fix For: 2.1.4
>
>
> 'nodetool status' self documents the node status with the statement 'Status=Up/Down'
which corresponds to the 'U' and 'D' statuses in the first column of the node listing.
> There is also a very important '?' status that is not documented, which seems to appear
when a node is bootstrapping.
> Automation and deployment tools need to cope with nodes in this transition state, and
the first step is to inform them about it in the documentation.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message