[
https://issues.apache.org/jira/browse/HADOOP-3894?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Steve Loughran updated HADOOP-3894:
-----------------------------------
Attachment: hadoop-3894.patch
This updated patch
DFDClient
* routes stack traces through the logger on close()
* includes the path to the file in question when raising an exception due to
unable to get the blocks of a file. Instead of going
"Could not get block locations. Aborting..." , it now includes the filename:
Could not get block locations. Source file "/test/filename" - Aborting...
* tweaks TestMiniMRMapRedDebugScript to
-timeout on job execution.
-looks for the target string using contains(), so log4j configuration
complaints do not break the test
-uses constants for the strings and sleep times
> DFSClient chould log errors better, and provide better diagnostics
> ------------------------------------------------------------------
>
> Key: HADOOP-3894
> URL: https://issues.apache.org/jira/browse/HADOOP-3894
> Project: Hadoop Core
> Issue Type: Improvement
> Components: dfs
> Affects Versions: 0.19.0
> Reporter: Steve Loughran
> Assignee: Steve Loughran
> Priority: Trivial
> Fix For: 0.19.0
>
> Attachments: hadoop-3894.patch, hadoop-3894.patch
>
>
> In my test runs I see a stack trace from DFSClient, because it isn't logging
> through the log APIs in its close() method. It should use the logger, for
> better error reporting
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
