[
https://issues.apache.org/jira/browse/NIFI-78?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15062223#comment-15062223
]
Joseph Witt commented on NIFI-78:
---------------------------------
Oleg
Ok so interesting. It was my understanding that Thread.stop() was even not
guaranteed. If that is truly a thing that is pretty cool.
What is true though is the state of the flow file is safe - if we encounter a
stuck thread and a user says truly kill this - then we own/control the session
(by design) and we'll just roll it back. No harm no foul basically. In the
event that we cannot actually kill the thread we should place it into a naught
thread/quarantine pile and indeed track which processor it is from because I
agree with you it is a bug. What we're doing here does not solve the problem
of the stuck thread - i agree. But in many cases it will allow the user to
move on with life to an extent greater than they have available today.
> 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.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)
