[
https://issues.apache.org/jira/browse/HADOOP-4899?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chris Douglas updated HADOOP-4899:
----------------------------------
Status: Open (was: Patch Available)
* I think some of these are intentional. The metrics logs should go to the same
place, that the Child logs to the TaskTracker log is deliberate, as are the
test cases for filters. A few of the others make some sense, though they do
look suspicious.
* This should use the version of getLog taking a class, not a String, to avoid
exactly this issue.
> Mutliple times wrong class provided for logger instantiation
> ------------------------------------------------------------
>
> Key: HADOOP-4899
> URL: https://issues.apache.org/jira/browse/HADOOP-4899
> Project: Hadoop Core
> Issue Type: Bug
> Reporter: Jakob Homan
> Assignee: Jakob Homan
> Priority: Minor
> Attachments: HADOOP-4899.patch
>
>
> Working in PermissionChecker.java I noticed the wrong class was being
> provided for the logger instantiation (LOG =
> LogFactory.getLog(UserGroupInformation.class, should be
> LogFactory.getLog(PermissionChecker.class););. Probably a copy-and-paste
> mistake. I searched through the source files and found several other
> instances across the project of this error. This could cause problems when
> trying to examine the logs, as entries would appear to be coming from the
> incorrect class.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
