[
https://issues.apache.org/jira/browse/NIFI-1295?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15186226#comment-15186226
]
Rob Moran commented on NIFI-1295:
---------------------------------
Here's a scenario of how this could work in the UI. Please feel free to poke
holes.
* User clicks Stop
* If immediate stop cannot occur, prompt user with dialog. Dialog lists
processor(s?) name, says it cannot stop right now, and provides two options:
*# Wait it out, along with any information that may be helpful to make that
decision
*# Force stop the processor, along with any consequences that may occur from
doing so
If they choose option 1
* Dialog goes away, render a spinner/busy icon on the processor
* Hovering the processor will display a tooltip stating that it is attempting
to stop
* Clicking the processor brings up original dialog
If they choose option 2
* Dialog goes away, processor status changes to stopped
OR
Alternate option 2
* Keep dialog open
* Confirm processor has stopped and what happened as a result
* User acknowledges to close dialog
* Processor status changes to stopped
> Add UI option to interrupt a running processor
> ----------------------------------------------
>
> Key: NIFI-1295
> URL: https://issues.apache.org/jira/browse/NIFI-1295
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Core UI
> Affects Versions: 0.4.0
> Reporter: Oleg Zhurakousky
> Assignee: Matt Gilman
>
> Basically we need an expose option to a user to kill Processors that can't be
> shut down the usual way (see NIFI-78 for more details).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
