hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-4451) hdfs balancer command returns exit code 1 on success instead of 0
Date Fri, 01 Feb 2013 10:47:18 GMT

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

Hudson commented on HDFS-4451:
------------------------------

Integrated in Hadoop-Yarn-trunk #114 (See [https://builds.apache.org/job/Hadoop-Yarn-trunk/114/])
    Change incorrect jira number HDFS-4151 to HDFS-4451 and move it to incompatible section.
(Revision 1441123)

     Result = SUCCESS
suresh : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1441123
Files : 
* /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt

                
> hdfs balancer command returns exit code 1 on success instead of 0
> -----------------------------------------------------------------
>
>                 Key: HDFS-4451
>                 URL: https://issues.apache.org/jira/browse/HDFS-4451
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: balancer
>    Affects Versions: 2.0.2-alpha
>         Environment: Centos 6.3, JDK 1.6.0_25
>            Reporter: Joshua Blatt
>             Fix For: 2.0.3-alpha
>
>         Attachments: HDFS-4451.patch, HDFS-4451.patch, HDFS-4451.patch
>
>
> Though the org.apache.hadoop.util.Tool interface javadocs indicate  implementations should
return 0 on success, the org.apache.hadoop.hdfs.server.balance.Balancer.Cli implementation
returns the int values of this enum instead:
>   // Exit status
>   enum ReturnStatus {
>     SUCCESS(1),
>     IN_PROGRESS(0),
>     ALREADY_RUNNING(-1),
>     NO_MOVE_BLOCK(-2),
>     NO_MOVE_PROGRESS(-3),
>     IO_EXCEPTION(-4),
>     ILLEGAL_ARGS(-5),
>     INTERRUPTED(-6);
> This created an issue for us when we tried to run the hdfs balancer as a cron job.  
Cron sends emails whenever a executable it runs exits non-zero.   We'd either have to disable
all emails and miss real issues or fix this bug.
> I think both SUCCESS and IN_PROGRESS ReturnStatuses should lead to exit 0.
> Marking this change as incompatible because existing scripts which interpret exit 1 as
success will be broken (unless they defensively/liberally interpret both exit 1 and exit 0
as success).

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message