[jira] [Updated] (BIGTOP-1125) Return value does not reflect status checks

["Sean Mackrory (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/BIGTOP-1125?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Sean Mackrory updated BIGTOP-1125:
----------------------------------

    Attachment: 0001-BIGTOP-1125.-Return-value-does-not-reflect-status-ch.patch

I've tested the start, stop, restart and status commands for a single process. I've also tested these operations with multiple operations, and all looks good. Note that if you run the status command and multiple processes are running, it will (correctly, IMO) report success as long as the processes it can find a trace of are running. It will report failure if you specify a process that has previously been shut down.

> Return value does not reflect status checks
> -------------------------------------------
>
>                 Key: BIGTOP-1125
>                 URL: https://issues.apache.org/jira/browse/BIGTOP-1125
>             Project: Bigtop
>          Issue Type: Bug
>    Affects Versions: 0.6.0
>            Reporter: Sean Mackrory
>            Assignee: Sean Mackrory
>             Fix For: 0.8.0
>
>         Attachments: 0001-BIGTOP-1125.-Return-value-does-not-reflect-status-ch.patch
>
>
> The init script for HBase RegionServers that supports multiple processes is always returning 0. It should return 0 on success of non-zero on failure. In the case of running multiple processes, failure is defined as a failure 
> There are already different constants defined in the file (e.g. different values for failures in all process, failures in some processes, failures in no processes... etc.), we just need to return them properly.
> Although this affects the 0.7.0 RC, I don't consider it a big enough deal to warrant -1'ing the RC, which I'm still testing.



--
This message was sent by Atlassian JIRA
(v6.1#6144)