[
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 patch removes the spurious commented line.
This patch does three things
-moves DFSClient to use the log API, rather than stderr when errors occur -and
to print the filename that is at fault-
-tweaks the test case to look for the "Bailing out" message anywhere in the
output, so if log4j decides to say something, it doesn't break the test.
-adds timeouts if the tests take too long. Yes, Ant does this but ant just
kills the process and destroys any XML content being generated, so tools like
hudson dont deal with such deaths well.
> 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, 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.
