https://jira.opendaylight.org This file is an XML representation of an issue en-us 8.20.10 820010 22-06-2022 https://jira.opendaylight.org/browse/ODLPARENT-154 odlparent <p>Upstream equivalent of <a href="https://bugzilla.redhat.com/show_bug.cgi?id=1570083" class="external-link" target="_blank" rel="nofollow noopener">https://bugzilla.redhat.com/show_bug.cgi?id=1570083</a> :</p> <p>It looks like in the recent odlparent bump and Karaf upgrade we went to a very small karaf.log file size, which with our default of logging at INFO level is typically too small and leads to much rotation in real world usage.</p> <p>Let's bump this from 16 MB to 10 GB:</p> <p><tt>log4j2.appender.rolling.policies.size.size = 16MB</tt></p> ODLPARENT-154

ODL karaf.log should rotate at 64MB instead of 16 MB

Bug Medium Resolved Done Robert Varga Michael Vorburger Tue, 24 Apr 2018 15:57:15 +0000 Fri, 15 Mar 2019 08:43:23 +0000 Fri, 15 Mar 2019 08:43:23 +0000 5.0.0 0 2 <p>Just a quick test just to make sure Log4j actually works :smiley: like this:</p> <p>In <tt>etc/org.ops4j.pax.logging.cfg</tt> replace the current <tt>16MB</tt> default with <tt>1KB</tt>:</p> <p><tt>log4j2.appender.rolling.policies.size.size = 1KB</tt></p> <p>and the <tt>odlparent/karaf/test-distribution creates log/karaf.log.1-7</tt> - great.</p> <p>So let's create a patch that does this.</p> <p>FTR: There is some noteworthy discussion about the best default log file size in the comments of c/71300.</p> <p>Unassigning issue from me, as I am not sure how to unblock the confusion that has meanwhile ensued on c/71300.</p> <p>We are just going to apply what works for us downstream - it's easy enough.</p> <p>I think 10GiB is rather aggressive, but we certainly can increase the size a bit.</p> Blocks ODLPARENT-153 Development Rank 0|i03dtr: