Details
-
Improvement
-
Status: Resolved
-
Minor
-
Resolution: Fixed
-
2.7.3
-
None
-
Reviewed
Description
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
Attachments
Attachments
Issue Links
- is depended upon by
-
HADOOP-11694 Über-jira: S3a phase II: robustness, scale and performance
- Resolved
- is related to
-
HADOOP-12636 Prevent ServiceLoader failure init for unused FileSystems
- Closed