[
https://issues.apache.org/jira/browse/NIFI-2032?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15343153#comment-15343153
]
ASF GitHub Bot commented on NIFI-2032:
--------------------------------------
Github user alopresto commented on the issue:
https://github.com/apache/nifi/pull/554
I fixed an issue in `GetSNMPTest` (a local variable was referenced from
within an inner class, and wasn't declared `final`). I forgot to squash it with
the commit that closed the PR. It was commit
[`aeb07124d13e09a18a2f3085269f614a5d1ef710`](https://github.com/apache/nifi/commit/aeb07124d13e09a18a2f3085269f614a5d1ef710).
> 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)
