[
https://issues.apache.org/jira/browse/NIFI-10001?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17538989#comment-17538989
]
ASF subversion and git services commented on NIFI-10001:
--------------------------------------------------------
Commit 88e53eae8ca1869bcf87d199dbef311080ac7a1e in nifi's branch
refs/heads/main from markap14
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=88e53eae8c ]
NIFI-10001: Fixed bugs that caused some components to not have their scheduled
state updated. (#6049)
* NIFI-10001: Fixed issue in which some components may fail to update the
scheduled state when comparing flows
* NIFI-10001: Fixed bugs that caused some components to not have their
scheduled state updated. When comparing two flows, now allow specifying how to
determine a VersionedComponent's ID for comparison. When comparing local flow
against flow from registry, use Versioned Component ID. But when comparing two
instantiated flows, such as local flow vs. cluster flow, use the
VersionedComponent's Instance ID instead. This ensures that we can properly
compare two components even if there are several instances of a given flow
> Nifi 1.16.1 trouble starting up due to controller services
> -----------------------------------------------------------
>
> Key: NIFI-10001
> URL: https://issues.apache.org/jira/browse/NIFI-10001
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core Framework
> Affects Versions: 1.16.1
> Reporter: MohammadReza Khedri
> Priority: Major
> Fix For: 1.17.0, 1.16.2
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> I updated *Apache Nifi* to version *1.16.1* from 1.16.0 today and it took
> about half an hour to run.
> I looked at the logs and realized that activating the controllers takes a
> long time. And I had a lot of controllers in my flows.
> So I re-installed the NIFI to the previous version and saw no problems and
> all the flows ran as quickly as possible.
>
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
