[jira] [Commented] (NIFI-9289) Startup time is very slow if there are enabled Controller Services that are invalid

["ASF subversion and git services (Jira)" <ji...@apache.org>]

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

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

Commit 231dd57e11d455c7015bafba2c0657b8f6921306 in nifi's branch refs/heads/main from Mark Payne
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=231dd57 ]

NIFI-9289: On startup, when enabling a Controller Service & its dependencies, do not wait for the dependencies to fully enable. Doing so can take 30 seconds per each Controller Service (and per each reference). Due to some previous refactoring, this waiting period is no longer necessary, as the referencing service can now be enabled and will asynchronously complete the enabling once it becomes valid (due to the referenced service becoming enabled).

Signed-off-by: Joe Gresock <jg...@gmail.com>

This closes #5449.


> Startup time is very slow if there are enabled Controller Services that are invalid
> -----------------------------------------------------------------------------------
>
>                 Key: NIFI-9289
>                 URL: https://issues.apache.org/jira/browse/NIFI-9289
>             Project: Apache NiFi
>          Issue Type: Bug
>          Components: Core Framework
>            Reporter: Mark Payne
>            Assignee: Mark Payne
>            Priority: Major
>             Fix For: 1.15.0
>
>          Time Spent: 1h
>  Remaining Estimate: 0h
>
> If we restart NiFi, and there are controller services that are enabled but not valid, the framework will wait for 30 seconds for the service to become enabled before giving up and moving on.
> This is not a very typical scenario, as it means that the service was valid before nifi was restarted. However, if a flow is copied from another NiFi instance, we can get into this situation in which it can take an extremely long time to startup.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)