[
https://issues.apache.org/jira/browse/HADOOP-3894?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12664469#action_12664469
]
Steve Loughran commented on HADOOP-3894:
----------------------------------------
Yes, I've just been making sure that all the tests are passing
I will separate the timeout issue,though I do prefer having tests time out with
meaningful diagnostics rather than killing the process.
The logging issue there is probably due to me not having a log4.properties in
my own hadoop.jar; it was interfering with other apps. I am probably the only
person getting told off from Log4J for not having a config file, which is
really something log4j should stop complaining about.
> 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.21.0
>
> Attachments: hadoop-3894.patch, 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.
