You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Tyler Hobbs (JIRA)" <ji...@apache.org> on 2015/06/09 21:31:00 UTC
[jira] [Commented] (CASSANDRA-9569) nodetool should exit with
status code != 0 if NodeProbe fails
[ https://issues.apache.org/jira/browse/CASSANDRA-9569?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14579448#comment-14579448 ]
Tyler Hobbs commented on CASSANDRA-9569:
----------------------------------------
I think your ccm master branch is behind. I made a change so that an exception is raised when nodetool has a non-zero exit status a couple of months ago: https://github.com/pcmanus/ccm/commit/10e8438c5c42d9fbbb3dcd168191a86f99fa9c70
> nodetool should exit with status code != 0 if NodeProbe fails
> -------------------------------------------------------------
>
> Key: CASSANDRA-9569
> URL: https://issues.apache.org/jira/browse/CASSANDRA-9569
> Project: Cassandra
> Issue Type: Bug
> Reporter: Marcus Eriksson
> Assignee: Marcus Eriksson
> Fix For: 3.x, 2.1.x, 2.2.x
>
>
> in 2.0 we exit with status code > 0 if NodeProbe.failed is set, in 2.1+ we ignore it.
> Also, dtest (or, ccm) ignore the exit code of nodetool.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)