[
https://issues.apache.org/jira/browse/BOOKKEEPER-684?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13769211#comment-13769211
]
Jiannan Wang commented on BOOKKEEPER-684:
-----------------------------------------
I just think disabling all zk INFO log is excessive. Since only few zk log is
annoying while some other zk INFO logs are helpful for debugging. If we
encounter issue that is hard to be reproduced, such zk logging would be
meaningful.
> ZK logging is oververbose, can cause oom in tests
> -------------------------------------------------
>
> Key: BOOKKEEPER-684
> URL: https://issues.apache.org/jira/browse/BOOKKEEPER-684
> Project: Bookkeeper
> Issue Type: Bug
> Reporter: Ivan Kelly
> Assignee: Jiannan Wang
> Priority: Trivial
> Fix For: 4.2.2
>
> Attachments:
> 0001-BOOKKEEPER-684-ZK-logging-is-oververbose-can-cause-o.patch,
> BOOKKEEPER-684.patch
>
>
> Some tests, GcLedgerTests for example, create a lot of ledgers (30k) which
> causes a lot of zk writes. This causes a lot of zk logging, which can fill
> the log buffer and cause an oom when you're running with very little memory.
> Fix is trivial. zk should be set to only log at error level in
> log4j.properties.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
