[
https://issues.apache.org/jira/browse/AMBARI-13471?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14963802#comment-14963802
]
Hudson commented on AMBARI-13471:
---------------------------------
FAILURE: Integrated in Ambari-branch-2.1 #709 (See
[https://builds.apache.org/job/Ambari-branch-2.1/709/])
AMBARI-13471 ZooKeeper "log4j.rootLogger" should have ROLLINGFILE (dsen:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=8fb899dbcb063bb62846b5222f4f053153cda9f4])
*
ambari-server/src/main/java/org/apache/ambari/server/upgrade/UpgradeCatalog213.java
*
ambari-server/src/test/java/org/apache/ambari/server/upgrade/UpgradeCatalog213Test.java
*
ambari-server/src/main/resources/stacks/BIGTOP/0.8/services/ZOOKEEPER/configuration/zookeeper-log4j.xml
> 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)
