[
https://issues.apache.org/jira/browse/NIFI-443?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14369512#comment-14369512
]
Joseph Witt edited comment on NIFI-443 at 3/19/15 3:19 PM:
-----------------------------------------------------------
mark - i reviewed the code. Applied the patch locally. Tested funnels with
clone and back pressure. Restarted with auto resume false. More testing. All
looks good. +1
was (Author: joewitt):
mark - i reviewed the code. Applied the patch locally. Tested funnels with
clone and back pressure. Restarted with auto resume false. More testing. All
looks good.
> Funnels can become permanently stopped.
> ---------------------------------------
>
> Key: NIFI-443
> URL: https://issues.apache.org/jira/browse/NIFI-443
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core Framework
> Affects Versions: 0.0.1
> Reporter: Matthew Clarke
> Priority: Critical
> Fix For: 0.1.0
>
> Attachments:
> 0001-NIFI-443-Always-start-funnels-when-added-to-process-.patch
>
>
> Funnels can become permanently stopped if they are loaded from a template or
> if NiFi is ever restarted with nifi.flowcontroller.autoResumeState= is set to
> false.
> The only way to get data flowing again is to replace the permanently stopped
> funnels with new funnels. There is no way to select a funnel and hit play
> (ineligible component).
> Templates that contain funnels are not usable without being manually fixed
> after addition to the graph.
> If a NiFi instance is ever restarted with auto resume state set to false,
> every funnel on the graph will need to be replaced.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
