[
https://issues.apache.org/jira/browse/NIFI-10703?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17634598#comment-17634598
]
ASF subversion and git services commented on NIFI-10703:
--------------------------------------------------------
Commit 1b8cd8349ba31f96f2898a712611d20d538ba240 in nifi's branch
refs/heads/main from Nathan Gough
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=1b8cd8349b ]
NIFI-10703 - Updated VersionedDataflow to support MaxEventDrivenThreadCount
NIFI-10703 - Also setting the maxEventDrivenThreadCount on the controller when
using a versioned flow.
NIFI-10703 - Corrected to use getMaxEventDrivenThreadCount(), set a default
value for event driven thread count in VersionedDataflow
NIFI-10703 - Updated log message for setMaxThreadCount in FlowController.java
NIFI-10703 - Updated default value for maxEventDrivenThreadCount
NIFI-10703 - Set private for DEFAULT_MAX_EVENT_DRIVEN_THREAD_COUNT
Signed-off-by: Matthew Burgess <[email protected]>
This closes #6638
> Event Driven Thread Count resets on NiFi restart
> ------------------------------------------------
>
> Key: NIFI-10703
> URL: https://issues.apache.org/jira/browse/NIFI-10703
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core Framework
> Reporter: Mark Bean
> Assignee: Nathan Gough
> Priority: Minor
> Time Spent: 3h 10m
> Remaining Estimate: 0h
>
> The controller setting for Maximum Event Driven Thread Count is reset to "1"
> after restarting NiFi. This occurs because this property is not written to
> the flow.json.gz file; it is only present in the flow.xml.gz.
> Therefore, until this issue is reolved and the property added to the JSON, a
> work-around is to remove the flow.json.gz before restarting NiFi.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
