[jira] [Commented] (NIFI-11245) Allow Reducing Maximum Timer Driven Thread Count Without Restarting

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

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

Mark Payne commented on NIFI-11245:
-----------------------------------

Thanks [~exceptionfactory] . I changed the Jira type to Improvement and wording of summary to reflect that - given that this was the intention in the code, I'd say it was intentional and not a bug. Though it does make sense to allow this now.

> Allow Reducing Maximum Timer Driven Thread Count Without Restarting
> -------------------------------------------------------------------
>
>                 Key: NIFI-11245
>                 URL: https://issues.apache.org/jira/browse/NIFI-11245
>             Project: Apache NiFi
>          Issue Type: Improvement
>          Components: Core Framework
>    Affects Versions: 1.0.0, 1.20.0
>            Reporter: David Handermann
>            Assignee: David Handermann
>            Priority: Minor
>             Fix For: 2.0.0
>
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> 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)