[jira] [Commented] (NIFI-1696) Event driven tasks appear not to auto restart when data in queues but no new data

["Dennis Jaheruddin (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/NIFI-1696?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17141232#comment-17141232 ] 

Dennis Jaheruddin commented on NIFI-1696:
-----------------------------------------

This issue is listed as critical, but it seems that nobody suffered from it since Nifi 0.6. (And also, is it really that bad to have to re-start a processor if you fixed a config problem for it?)

 

Recommending to either close or de-prioritize this issue.

> Event driven tasks appear not to auto restart when data in queues but no new data
> ---------------------------------------------------------------------------------
>
>                 Key: NIFI-1696
>                 URL: https://issues.apache.org/jira/browse/NIFI-1696
>             Project: Apache NiFi
>          Issue Type: Bug
>    Affects Versions: 0.6.0
>            Reporter: Joe Witt
>            Priority: Critical
>
> The scenario:
> - 3 node cluster
> - node 'NodeA' is primary and running a processor 'ProcP1' set to event driven scheduling
> - 'ProcP1' wasn't working due to a config issue but there were a few events on its input queues.
> - restarted node 'NodeA' after fixing config issue.
> - No new events had come in but those events were sitting there.
> Result: The 'ProcP1' appears to be in scheduled state but does not get scheduled to run - perhaps because no new event triggered it?  Seems like perhaps we're not checking if there are already events at restart?  Stopping and starting 'ProcP1' then resulted in things going back to normal.
> It is not obvious to me how to recreate this in a repeatable way.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)