You are viewing a plain text version of this content. The canonical link for it is here.

Posted to common-issues@hadoop.apache.org by "Tom White (JIRA)" <ji...@apache.org> on 2011/03/02 18:11:39 UTC

[jira] Updated: (HADOOP-7114) FsShell should dump all exceptions at DEBUG level

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

Tom White updated HADOOP-7114:
------------------------------

       Resolution: Fixed
    Fix Version/s: 0.23.0
     Hadoop Flags: [Reviewed]
           Status: Resolved  (was: Patch Available)

+1 I've just committed this. Thanks Todd!

> FsShell should dump all exceptions at DEBUG level
> -------------------------------------------------
>
>                 Key: HADOOP-7114
>                 URL: https://issues.apache.org/jira/browse/HADOOP-7114
>             Project: Hadoop Common
>          Issue Type: Improvement
>          Components: fs
>    Affects Versions: 0.23.0
>            Reporter: Todd Lipcon
>            Assignee: Todd Lipcon
>            Priority: Minor
>             Fix For: 0.23.0
>
>         Attachments: hadoop-7114.txt
>
>
> Most of the FsShell commands catch exceptions and then just print out an error like "foo: " + e.getLocalizedMessage(). This is fine when the exception is "user-facing" (eg permissions errors) but in the case of a user hitting a bug you get a useless error message with no stack trace. For example, something "chmod: null" in the case of a NullPointerException bug.
> It would help debug these cases for users and developers if we also logged the exception with full trace at DEBUG level.

-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira