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

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

Commit 88d2c03b37d6cdabd260658c84e4305b4fa14c99 in nifi's branch 
refs/heads/support/nifi-1.x from David Handermann
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=88d2c03b37 ]

NIFI-11245 Corrected reducing Maximum Thread Count while running (#7005)

- Corrected implementation to allow reducing Maximum Thread Count below the 
default of 10

> 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, 1.21.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)

Reply via email to