[
https://issues.apache.org/jira/browse/NIFI-78?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15185066#comment-15185066
]
Oleg Zhurakousky commented on NIFI-78:
--------------------------------------
So, I am resuming the progress on this one and disassociating it wit the
existing https://github.com/apache/nifi/pull/210 since it turns out the PR
aside form refactoring solves a bit of a different issue (I'll update commit
message as well to reflect that). The new functionality to initiate interrupt
only applies to potential deadlocks during @OnScheduled invocation and not
during OnTrigger operations which is where the Session problem described by
Mark is occurring. I'll raise a separate JIRA for Session invalidation and
make it a pre-requisite to this one.
> 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
> Assignee: Oleg Zhurakousky
> Priority: Minor
> Fix For: 0.6.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)
