cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chris Goffinet (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-2721) nodetool statusthrift exception while node starts up
Date Mon, 30 May 2011 08:09:47 GMT

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

Chris Goffinet commented on CASSANDRA-2721:
-------------------------------------------

Ah! I forgot to commit that patch. It was put in our build. CASSANDRA-2722

> nodetool statusthrift exception while node starts up
> ----------------------------------------------------
>
>                 Key: CASSANDRA-2721
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-2721
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: Chris Goffinet
>            Assignee: Chris Goffinet
>            Priority: Trivial
>             Fix For: 0.8.1
>
>         Attachments: 0001-If-RPCServer-isn-t-started-just-return-false-instead.patch
>
>
> We noticed when calling nodetool statusthrift, while a node is starting up, it throws
an exception. I think the proper behavior should be just return false, instead of throwing
an exception if RPC server hasn't started yet. That way this stack trace won't have to be
thrown in nodetool:
> Exception in thread "main" 
> java.lang.IllegalStateException: No configured RPC daemon

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message