nifi-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <>
Subject [jira] [Commented] (NIFI-443) Funnels can become permanently stopped.
Date Fri, 27 Mar 2015 19:06:53 GMT


ASF subversion and git services commented on NIFI-443:

Commit 909ded32aaa4cc5f70b162792e9a4216357826e1 in incubator-nifi's branch refs/heads/develop
from [~markap14]
[;h=909ded3 ]

NIFI-443: Fixed out-of-date comments/documentation

> Funnels can become permanently stopped.
> ---------------------------------------
>                 Key: NIFI-443
>                 URL:
>             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,
0001-NIFI-443-If-a-funnel-is-given-an-incoming-connection.patch, 0002-NIFI-443-Removed-stopFunnel-from-ProcessGroup-becaus.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

View raw message