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 "Steve Loughran (JIRA)" <ji...@apache.org> on 2016/06/27 13:55:52 UTC

[jira] [Updated] (HADOOP-13323) Downgrade stack trace on FS load from Warn to debug

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

Steve Loughran updated HADOOP-13323:
------------------------------------
    Attachment: HADOOP-13323-branch-2-001.patch

Patch 001

logs at WARN all the exception messages, but only does the stack trace at DEBUG.

test cleaned up slightly, but the new code doesn't actually get directly checked. 

> Downgrade stack trace on FS load from Warn to debug
> ---------------------------------------------------
>
>                 Key: HADOOP-13323
>                 URL: https://issues.apache.org/jira/browse/HADOOP-13323
>             Project: Hadoop Common
>          Issue Type: Improvement
>          Components: fs
>    Affects Versions: 2.7.3
>            Reporter: Steve Loughran
>            Assignee: Steve Loughran
>            Priority: Minor
>         Attachments: HADOOP-13323-branch-2-001.patch
>
>
> HADOOP-12636 catches exceptions on FS creation, but prints a stack trace @ warn every time..this is noisy and irrelevant if the installation doesn't need connectivity to a specific filesystem or object store.
> I propose: only printing the toString values of the exception chain @ warn; the full stack comes out at debug.
> We could some more tuning: 
> * have a specific log for this exception, which allows installations to turn even the warnings off.
> * add a link to a wiki page listing the dependencies of the shipped filesystems



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: common-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-issues-help@hadoop.apache.org