[
https://issues.apache.org/jira/browse/NIFI-78?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15060888#comment-15060888
]
Joseph Witt commented on NIFI-78:
---------------------------------
so what i contend is that while we cannot stop threads we can isolate the
impact of them. At a framework level we can rollback and disconnect their
session and ability to interact with anything else should they ever get out of
their stuck state and we can move on. We can basically quarantine them to be
of minimal impact. We can let the user know how many threads are in a
quarantined stated because in theory eventually a restart would be required.
> 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)
