ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMBARI-13926) AMS log file not getting created
Date Tue, 17 Nov 2015 22:43:11 GMT

    [ https://issues.apache.org/jira/browse/AMBARI-13926?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15009749#comment-15009749
] 

Hadoop QA commented on AMBARI-13926:
------------------------------------

{color:green}+1 overall{color}.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12772835/AMBARI-13926.patch
  against trunk revision .

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

    {color:green}+1 tests included{color}.  The patch appears to include 19 new or modified
test files.

    {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-metrics/ambari-metrics-timelineservice.

Test results: https://builds.apache.org/job/Ambari-trunk-test-patch/4312//testReport/
Console output: https://builds.apache.org/job/Ambari-trunk-test-patch/4312//console

This message is automatically generated.

> AMS log file not getting created
> --------------------------------
>
>                 Key: AMBARI-13926
>                 URL: https://issues.apache.org/jira/browse/AMBARI-13926
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-metrics
>    Affects Versions: 2.1.2
>            Reporter: Aravindan Vijayan
>            Assignee: Aravindan Vijayan
>            Priority: Critical
>             Fix For: 2.1.3
>
>         Attachments: AMBARI-13926.patch
>
>
> The AMS logs were not getting created because the wrong log4j.properties were getting
picked up. 
> Fix
> Moved the code that had a dependency on the jar that supplied the wrong log4j.properties
to src/test. Hence, the jar will not be packaged during AMS jar assembly.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message