[jira] [Updated] (NIFI-9434) Controller level bulletin when content repository backpressure

["Mark Payne (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/NIFI-9434?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Mark Payne updated NIFI-9434:
-----------------------------
    Fix Version/s: 1.16.0
       Resolution: Fixed
           Status: Resolved  (was: Patch Available)

> Controller level bulletin when content repository backpressure
> --------------------------------------------------------------
>
>                 Key: NIFI-9434
>                 URL: https://issues.apache.org/jira/browse/NIFI-9434
>             Project: Apache NiFi
>          Issue Type: Improvement
>            Reporter: Lehel Boér
>            Assignee: Lehel Boér
>            Priority: Major
>             Fix For: 1.16.0
>
>          Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> We see more and more users hitting the situation where NiFi seems stuck because of the content repo back pressure mechanism that is set by default. We should have a controller level bulletin to let the users know what is happening.
> This usually happens when all repositories and OS data are using the same file system and usage goes over 52%.
> If nifi.content.repository.archive.max.usage.percentage is 50% (default value) and nifi.content.repository.archive.backpressure.percentage is not set, the effective value of nifi.content.repository.archive.backpressure.percentage will be 52%.
> This property is used to control the content repository disk usage percentage at which backpressure is applied to the processes writing to the content repository. Once this percentage is reached, the content repository will refuse any additional writes. Writes will be refused until the archive delete process has brought the content repository disk usage percentage below nifi.content.repository.archive.max.usage.percentage.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)