[
https://issues.apache.org/jira/browse/AMBARI-13471?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14963401#comment-14963401
]
Hadoop QA commented on AMBARI-13471:
------------------------------------
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12767346/AMBARI-13471.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 1 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-server.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/3999//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/3999//console
This message is automatically generated.
> ZooKeeper "log4j.rootLogger" should have ROLLINGFILE instead of CONSOLE
> -----------------------------------------------------------------------
>
> Key: AMBARI-13471
> URL: https://issues.apache.org/jira/browse/AMBARI-13471
> Project: Ambari
> Issue Type: Bug
> Components: stacks
> Affects Versions: 2.1.2
> Reporter: Dmytro Sen
> Assignee: Dmytro Sen
> Priority: Critical
> Fix For: 2.1.3
>
> Attachments: AMBARI-13471.patch
>
>
> Currently ZooKeeper's root logger is INFO and CONSOLE. The problem with
> CONSOLE is that there is no file limit and the _zookeeper.out_ file can get
> really large. Ambari needs to change ZooKeeper's default log4j configuration
> to use ROLLINGFILE instead of CONSOLE.
> {code}
> log4j.rootLogger=INFO, ROLLINGFILE
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
