hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-4134) hadoop namenode & namenode entry points should return -1 exit code on bad arguments
Date Fri, 02 Nov 2012 12:05:12 GMT

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

Hadoop QA commented on HDFS-4134:
---------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12551850/HDFS-4134.patch
  against trunk revision .

    {color:red}-1 patch{color}.  The patch command could not apply the patch.

Console output: https://builds.apache.org/job/PreCommit-HDFS-Build/3439//console

This message is automatically generated.
                
> hadoop namenode & namenode entry points should return -1 exit code on bad arguments
> -----------------------------------------------------------------------------------
>
>                 Key: HDFS-4134
>                 URL: https://issues.apache.org/jira/browse/HDFS-4134
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: name-node
>    Affects Versions: 1.0.4
>            Reporter: Steve Loughran
>            Priority: Minor
>         Attachments: HDFS-4134.patch
>
>
> When you go  {{hadoop namenode start}} (or some other bad argument to the namenode),
a usage message is generated -but the script returns 0. 
> This stops it being a robust command to invoke from other scripts -and is inconsistent
with the JT & TT entry points, that do return -1 on a usage message

--
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