hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Karam Singh (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-3151) Hod should have better error messages.
Date Mon, 16 Jun 2008 07:53:45 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-3151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12605214#action_12605214
] 

Karam Singh commented on HADOOP-3151:
-------------------------------------

Check and found that now hod throws mesages similar as mention by vinod, but its better if
avoid using word invalied e.g -
error message for script file which not executable can be modifed 
  Invalid script file (--hod.script or -s) : <path to a non-executable file> : Not an
executable. - for script file which not executable
to 
 Script <path to  non executabe file> is not an executable.
Similarly we can change Invalid script file (--hod.script or -s) : <path to a dir> :
Not a file. to "Script <path to dir> is not a file. etc.

> Hod should have better error messages.
> --------------------------------------
>
>                 Key: HADOOP-3151
>                 URL: https://issues.apache.org/jira/browse/HADOOP-3151
>             Project: Hadoop Core
>          Issue Type: Bug
>          Components: contrib/hod
>    Affects Versions: 0.16.3
>            Reporter: Arkady Borkovsky
>            Assignee: Vinod Kumar Vavilapalli
>             Fix For: 0.18.0
>
>         Attachments: HADOOP-3151
>
>
> (1)
> gsgw1037:/homes/arkady/CDSR> hod allocate -n 4 -d xx
> error: bin/hod failed to start.
> error: invalid 'clusterdir' specified in section hod (--hod.clusterdir): xx
> error: 1 problem found.
> Check your command line options and/or your configuration file /grid/0/kryptonite/hod/conf/hodrc
>    * Directory 'xx' does not exist - the message shuold say "Non-existing directory"
(or "directory not found"), not "invalid"
>    * checking the configuration file will not help, the advice is confusing
>    * checking the command line options is the obvious thing to do -- the advise is unnecessary.
> (2) when hod does not understand the command, it prints the whole help options message
-- which clobbers the screen and is confusing. It should give a meaningful message -- and
may say "type hod help for more info"

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message