[
https://issues.apache.org/jira/browse/HADOOP-13323?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chris Nauroth updated HADOOP-13323:
-----------------------------------
Resolution: Fixed
Hadoop Flags: Reviewed
Fix Version/s: 2.8.0
Status: Resolved (was: Patch Available)
+1 for the patch. In addition to the unit test, I did some manual testing by
hacking up a deployment of the distro with a mangled classpath. The patch
worked as advertised, with the messages at warn level and the full stack trace
appearing after I switched on debug logging. I committed this to trunk,
branch-2 and branch-2.8. Steve, thank you.
> 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
> Fix For: 2.8.0
>
> 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: [email protected]
For additional commands, e-mail: [email protected]
