You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "Eric Secules (Jira)" <ji...@apache.org> on 2025/07/11 17:26:00 UTC
[jira] [Created] (NIFI-14745) Cache PG violations and add progressive backoff too validator task
Eric Secules created NIFI-14745:
-----------------------------------
Summary: Cache PG violations and add progressive backoff too validator task
Key: NIFI-14745
URL: https://issues.apache.org/jira/browse/NIFI-14745
Project: Apache NiFi
Issue Type: Sub-task
Reporter: Eric Secules
Add a read-through cache for PG violations. Delete the entire cache each time validations change since they are nested and the RuleViolationsManager doesn't know the topology of the flow. This will help because violations don't change unless the config changes, so we'll only take a performance hit after a config change. Each subsequent access will be O(1) in terms of process groups.
Add a progressive backoff between validation passes so that if a lot of flow changes are happening at once we don't get stuck in a vicious cycle of validating the flow every 5 seconds. If there were flow changes in the current validation pass increase the delay (either linear or exponential) before the next validation pass up until a maximum. If there were no config changes in this current pass, reset the delay to the minimum (5 seconds).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)