[
https://issues.apache.org/jira/browse/NIFI-2032?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15342363#comment-15342363
]
ASF GitHub Bot commented on NIFI-2032:
--------------------------------------
GitHub user olegz opened a pull request:
https://github.com/apache/nifi/pull/554
NIFI-2032 port for 0.x
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/olegz/nifi NIFI-2032-0.x
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/nifi/pull/554.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #554
----
commit 4996856f1df1ed8a18850c3faca964e827b60cbc
Author: Oleg Zhurakousky <[email protected]>
Date: 2016-06-17T16:08:26Z
NIFI-2032 port for 0.x
----
> Processors could be started before the Controller Services that they depend on
> ------------------------------------------------------------------------------
>
> Key: NIFI-2032
> URL: https://issues.apache.org/jira/browse/NIFI-2032
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core Framework
> Reporter: Mark Payne
> Assignee: Oleg Zhurakousky
> Priority: Critical
> Fix For: 1.0.0, 0.7.0
>
>
> in the StandardControllerServiceProvider, we enable a Collection of
> Controller Services but do so in the background with a limited number of
> threads. We need to ensure that all Controller Services have at least become
> ENABLING before returning from this method. Otherwise, Processors that depend
> on them could attempt to start. If this happens, the Processor will be
> invalid because it references a Disabled Controller Service. As a result, the
> Processor will not start. In a clustered environment, we will end up with
> inconsistent run states across the nodes.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
