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 "Chen Liang (JIRA)" <ji...@apache.org> on 2016/08/01 18:15:20 UTC
[jira] [Commented] (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:comment-tabpanel&focusedCommentId=15402554#comment-15402554 ]
Chen Liang commented on HADOOP-13323:
-------------------------------------
Hi [~stevel@apache.org],
I'm trying to dig into the failed test as you mentioned in HADOOP-12588. But the test results report seems to be lost, could you elaborate a bit more on the failed test?
thanks!
- Chen
> 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