[
https://issues.apache.org/jira/browse/YARN-2256?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14535269#comment-14535269
]
Zhijie Shen commented on YARN-2256:
-----------------------------------
I kindly agree with Allen. If we want logSuccess of NM audit logs, we're
considering them as equivalently important as other component's audit logs. It
may not be a good idea if logSuccess in other place shows up at INFO level, but
doesn't in NM.
I checked the usage of logSuccess in NM. I think it's necessary to logSuccess
for starting/stopping containers. Another place where logSuccess is used is the
lifecycle of container. Not sure if that is important too, as RM app/attempt
doesn't log this. /cc [~zxu].
So what's the major NM audit logs do you see in your environment? Shall we try
to avoid unnecessary logSuccess instead of changing the log level?
> Too many nodemanager and resourcemanager audit logs are generated
> -----------------------------------------------------------------
>
> Key: YARN-2256
> URL: https://issues.apache.org/jira/browse/YARN-2256
> Project: Hadoop YARN
> Issue Type: Bug
> Components: nodemanager, resourcemanager
> Affects Versions: 2.4.0
> Reporter: Varun Saxena
> Assignee: Varun Saxena
> Labels: BB2015-05-TBR
> Attachments: YARN-2256.patch
>
>
> Following audit logs are generated too many times(due to the possibility of a
> large number of containers) :
> 1. In NM - Audit logs corresponding to Starting, Stopping and finishing of a
> container
> 2. In RM - Audit logs corresponding to AM allocating a container and AM
> releasing a container
> We can have different log levels even for NM and RM audit logs and move these
> successful container related logs to DEBUG.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
