You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@nifi.apache.org by "David Handermann (Jira)" <ji...@apache.org> on 2023/03/02 23:54:00 UTC

[jira] [Created] (NIFI-11245) Reducing Maximum Timer Driven Thread Count Requires Restarting

David Handermann created NIFI-11245:
---------------------------------------

             Summary: Reducing Maximum Timer Driven Thread Count Requires Restarting
                 Key: NIFI-11245
                 URL: https://issues.apache.org/jira/browse/NIFI-11245
             Project: Apache NiFi
          Issue Type: Bug
          Components: Core Framework
    Affects Versions: 1.20.0
            Reporter: David Handermann
            Assignee: David Handermann


The {{Maximum Timer Driven Thread Count}} property in NiFi Controller Settings specifies the total number of Threads that can be spawned and scheduled to run Processors using the default Timer Driven strategy. This setting can be changed on a running system, but reducing the number requires restarting NiFi to apply the changes.

The method responsible for updating the internal Thread Pool size does not allow reducing the core pool size at runtime, which also blocks reducing the Maximum Count below the default value of 10.



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