You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "ASF subversion and git services (Jira)" <ji...@apache.org> on 2023/11/13 16:50:00 UTC

[jira] [Commented] (NIFI-11788) Make adjustments to logback.xml to nudge logback into more consistent cleanup behavior

    [ https://issues.apache.org/jira/browse/NIFI-11788?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17785576#comment-17785576 ] 

ASF subversion and git services commented on NIFI-11788:
--------------------------------------------------------

Commit 6447aea2583eec08e44f40b3ad8371d15965f25c in nifi's branch refs/heads/main from Mike Thomsen
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=6447aea258 ]

NIFI-11788 Modified APP_FILE logback configuration to have better cleanup
NIFI-11788 Standardized Logback maximum settings
- Set MiNiFi maxHistory to 10 and totalSizeCap to 10MB
- Set NiFi maxHistory to 30 and totalSizeCap to 3GB except for deprecation log
- Set Stateless maxHistory to 30 and totalSizeCap to 3GB
- Set Registry maxHistory to 30 and totalSizeCap to 3GB
NIFI-11788 Increased MiNiFi maxFileSize to 10MB and cap to 100MB

This closes #7465. Coauthored by David Handermann and Mike Thomsen

Signed-off-by: Joseph Witt <jo...@apache.org>


> Make adjustments to logback.xml to nudge logback into more consistent cleanup behavior
> --------------------------------------------------------------------------------------
>
>                 Key: NIFI-11788
>                 URL: https://issues.apache.org/jira/browse/NIFI-11788
>             Project: Apache NiFi
>          Issue Type: Improvement
>    Affects Versions: 1.latest, 2.latest
>            Reporter: Mike Thomsen
>            Assignee: Mike Thomsen
>            Priority: Major
>          Time Spent: 3h
>  Remaining Estimate: 0h
>
> A lot of users have been reporting problems with enforcing log rollover with logback. Disk overflow appears to be a common problem with this.
> Based on what I have found, it appears that there are two flags that need to be set on the appenders as appropriate: totalSizeCap and cleanHistoryOnStart. After experimenting with these settings, I found that with them enabled on the APP appender, they enforce log cleanup.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)