[
https://issues.apache.org/jira/browse/NIFI-10703?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17630646#comment-17630646
]
Nathan Gough commented on NIFI-10703:
-------------------------------------
I was able to confirm this issue, but I'm questioning whether leaving out the
event driven thread config from the flow.json was an intentional choice. It's
a relatively easy fix of adding a setter and getting to the versioned data flow
implementation, but I have a suspicion it was left out for a reason.
[~markap14] can you comment on this?
I guess we can try to find a way to not have this keep resetting on every
restart though.
> 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
> Affects Versions: 1.18.0
> Reporter: Mark Bean
> Assignee: Nathan Gough
> Priority: Minor
>
> 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)
