[
https://issues.apache.org/jira/browse/NIFI-78?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15176522#comment-15176522
]
Mark Payne commented on NIFI-78:
--------------------------------
I think one thing that we need to be sure to consider here, is what happens
after we interrupt a Processor, wrt the ProcessSession's. For example, if the
processor has a Session already, and it's interrupted, we should ensure that
the Processor can't access any FlowFiles. I.e., we need the ability to
invalidate all sessions for that Processor. This would probably involve
something like an invalidate() method being added to ProcessSession, and it
would mean that we must have an invalidate() method on ProcessSessionFactory.
ProcessSessionFactory should then delegate this to all Sessions that have been
created by it (should probably use a Weak Reference type of data structure so
that we can keep track of all sessions that have been created without
preventing GC from reclaiming it)
> 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)
