You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@nifi.apache.org by "Joseph Witt (JIRA)" <ji...@apache.org> on 2015/11/23 15:25:10 UTC

[jira] [Commented] (NIFI-78) Add interrupt option for stopped processors with active threads

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

Joseph Witt commented on NIFI-78:
---------------------------------

Had a user comment on ExecuteProcess being stuck.  The guidance to them is kind of brutal because they cannot fix the issue with the processor configuration unless it isn't running and to have it not running they have to restart NiFi with auto resume state false.  This isn't a particularly good user experience and we can do better.

We should add a kill/interrupt feature which immediately disconnects that processor's thread(s) and ensures whatever their results are ends up in rollback(s).  

> Add interrupt option for stopped processors with active threads
> ---------------------------------------------------------------
>
>                 Key: NIFI-78
>                 URL: https://issues.apache.org/jira/browse/NIFI-78
>             Project: Apache NiFi
>          Issue Type: Improvement
>          Components: Core Framework
>            Reporter: Joseph Witt
>            Priority: Minor
>             Fix For: 0.5.0
>
>
> Some processors have really long stopping periods.  Would be nice to be able to forcibly kill them if possible.  Otherwise certain flow changes cannot occur.  This is one part best practices and another part helping the user decide when to forcibly kill a processor.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)