[
https://issues.apache.org/jira/browse/NIFI-11245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17696212#comment-17696212
]
ASF subversion and git services commented on NIFI-11245:
--------------------------------------------------------
Commit 44c70277ea8d9059f145d5e3957ef7ab61db666e in nifi's branch
refs/heads/main from David Handermann
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=44c70277ea ]
NIFI-11245 Corrected reducing Maximum Thread Count while running (#7005)
- Corrected implementation to allow reducing Maximum Thread Count below the
default of 10
> 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.0.0, 1.20.0
> Reporter: David Handermann
> Assignee: David Handermann
> Priority: Minor
> 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)
