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 "Varun Saxena (JIRA)" <ji...@apache.org> on 2014/07/08 08:41:34 UTC
[jira] [Commented] (YARN-2256) Too many nodemanager audit logs are
generated
[ https://issues.apache.org/jira/browse/YARN-2256?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14054574#comment-14054574 ]
Varun Saxena commented on YARN-2256:
------------------------------------
I will make the following changes :
1. Create new logSuccess and logFailure methods having an additional parameter indicating log level. This can be an enum in RMAuditLogger and NMAuditLogger.
2. The previous logSuccess method in RMAuditLogger will continue printing logs at INFO level. The new method can be used to print logs at appropriate levels.
3. Change the container logs to DEBUG.
> Too many nodemanager 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
>
> 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.2#6252)