You are viewing a plain text version of this content. The canonical link for it is here.
Posted to yarn-issues@hadoop.apache.org by "Rohith (JIRA)" <ji...@apache.org> on 2015/02/12 19:30:11 UTC
[jira] [Commented] (YARN-3191) Log object should be initialized
with its own class
[ https://issues.apache.org/jira/browse/YARN-3191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14318708#comment-14318708 ]
Rohith commented on YARN-3191:
------------------------------
Attached the straight forward patch.Kindly review
> Log object should be initialized with its own class
> ---------------------------------------------------
>
> Key: YARN-3191
> URL: https://issues.apache.org/jira/browse/YARN-3191
> Project: Hadoop YARN
> Issue Type: Bug
> Components: nodemanager
> Affects Versions: 2.6.0
> Reporter: Rohith
> Assignee: Rohith
> Priority: Trivial
> Attachments: 0001-YARN-3191.patch
>
>
> In ContainerImpl and ApplicationImpl class, Log object is initialized with interface name. This causes in logging happen with interface class.
> {{private static final Log LOG = LogFactory.getLog(Container.class);}}
> {{private static final Log LOG = LogFactory.getLog(Application.class);}}
> it should be
> {{private static final Log LOG = LogFactory.getLog(ContainerImpl.class);}}
> {{private static final Log LOG = LogFactory.getLog(ApplicationImpl.class);}}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)