[ODLPARENT-154] ODL karaf.log should rotate at 64MB instead of 16 MB Created: 24/Apr/18 Updated: 15/Mar/19 Resolved: 15/Mar/19 |
|
| Status: | Resolved |
| Project: | odlparent |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 5.0.0 |
| Type: | Bug | Priority: | Medium |
| Reporter: | Michael Vorburger | Assignee: | Robert Varga |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Description |
|
Upstream equivalent of https://bugzilla.redhat.com/show_bug.cgi?id=1570083 : 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. Let's bump this from 16 MB to 10 GB: log4j2.appender.rolling.policies.size.size = 16MB |
| Comments |
| Comment by Michael Vorburger [ 25/Apr/18 ] |
|
Just a quick test just to make sure Log4j actually works :smiley: like this: In etc/org.ops4j.pax.logging.cfg replace the current 16MB default with 1KB: log4j2.appender.rolling.policies.size.size = 1KB and the odlparent/karaf/test-distribution creates log/karaf.log.1-7 - great. So let's create a patch that does this. |
| Comment by Michael Vorburger [ 26/Apr/18 ] |
|
FTR: There is some noteworthy discussion about the best default log file size in the comments of c/71300. |
| Comment by Michael Vorburger [ 14/May/18 ] |
|
Unassigning issue from me, as I am not sure how to unblock the confusion that has meanwhile ensued on c/71300. We are just going to apply what works for us downstream - it's easy enough. |
| Comment by Robert Varga [ 12/Mar/19 ] |
|
I think 10GiB is rather aggressive, but we certainly can increase the size a bit. |