ambari-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (JIRA)" <>
Subject [jira] [Commented] (AMBARI-17148) Fix rm.audit.logger and nm.audit.logger configuration setting for Yarn
Date Mon, 13 Jun 2016 15:10:21 GMT


Hadoop QA commented on AMBARI-17148:

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment
  against trunk revision .

    {color:green}+1 @author{color}.  The patch does not contain any @author tags.

    {color:red}-1 tests included{color}.  The patch doesn't appear to include any new or modified
                        Please justify why no new tests are needed for this patch.
                        Also please list what manual steps were performed to verify this patch.

    {color:green}+1 javac{color}.  The applied patch does not increase the total number of
javac compiler warnings.

    {color:green}+1 release audit{color}.  The applied patch does not increase the total number
of release audit warnings.

    {color:green}+1 core tests{color}.  The patch passed unit tests in ambari-server.

Test results:
Console output:

This message is automatically generated.

> Fix rm.audit.logger and nm.audit.logger configuration setting for Yarn
> ----------------------------------------------------------------------
>                 Key: AMBARI-17148
>                 URL:
>             Project: Ambari
>          Issue Type: Bug
>    Affects Versions: 2.4.0
>            Reporter: Yesha Vora
>            Priority: Critical
>         Attachments: AMBARI-17148.patch
> Ambari sets RMAUDIT and NMAUDIT loggers by default for YARN. 
> {code}rm.audit.logger=INFO,RMAUDIT
> ..
> nm.audit.logger=INFO,NMAUDIT
> ..{code}
> This config leads to log4j errors while running yarn-cli command. 
> {code}
>  yarn application -list
> log4j:ERROR setFile(null,true) call failed.
> /xx/nm-audit.log (No such file or directory)
> 	at Method)
> 	at
> 	at<init>(
> 	at<init>(
> 	at org.apache.log4j.FileAppender.setFile(
> 	at org.apache.log4j.FileAppender.activateOptions(
> 	at org.apache.log4j.DailyRollingFileAppender.activateOptions(
> 	at org.apache.log4j.config.PropertySetter.activate(
> 	at org.apache.log4j.config.PropertySetter.setProperties(
> 	at org.apache.log4j.config.PropertySetter.setProperties(
> 	at org.apache.log4j.PropertyConfigurator.parseAppender(
> 	at org.apache.log4j.PropertyConfigurator.parseCategory(
> 	at org.apache.log4j.PropertyConfigurator.parseCatsAndRenderers({code}
> In YARN's case, rm.audit.logger should be set when starting RM only and nm.audit.logger
when starting NMs only. 

This message was sent by Atlassian JIRA

View raw message