[
https://issues.apache.org/jira/browse/NIFI-2492?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15409543#comment-15409543
]
Joseph Witt commented on NIFI-2492:
-----------------------------------
[~devriesb] The notion of "I want this running" vs "I want this thing not
running" is really what is getting captured when you start or stop a processor
and that is what we must keep consistent in terms of managing the cluster. The
behavior that is intended for the case you've mentioned here should be that the
processor is told to start, it throws an exception, that gets logged and a
bulletin generated, and it will continue to try to start it over and over ever
30 seconds or until the processor is told to stop. Are you not seeing the
bulletin and not seeing it continue to try?
https://github.com/apache/nifi/blob/master/nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-framework-core/src/main/java/org/apache/nifi/controller/StandardProcessorNode.java#L1191-L1225
> Processor startup issue
> -----------------------
>
> Key: NIFI-2492
> URL: https://issues.apache.org/jira/browse/NIFI-2492
> Project: Apache NiFi
> Issue Type: Bug
> Reporter: Brandon DeVries
> Priority: Minor
>
> In the process of testing NIFI-2160 and NIFI-2344, we found that if a
> processor throws an Exception (e.g. IllegalStateException) from its
> @OnScheduled method, it will not resume its STARTED state. In a cluster,
> this could result in inconsistent state similar to NIFI-2491, and should
> either not be allowed to happen (terminate the instance), or should be made
> clear in the UI.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
