[
https://issues.apache.org/jira/browse/FLINK-2111?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14568994#comment-14568994
]
ASF GitHub Bot commented on FLINK-2111:
---------------------------------------
Github user mjsax commented on the pull request:
https://github.com/apache/flink/pull/750#issuecomment-107926235
Hi,
after thinking about the signal name again, I disagree. "terminate" does
not mean kill, but is a request to gracefully shut down. "stop" from my point
of view is too soft, as it does not indicates strongly enough, that the job is
completely shut down and "cleared". I would interpret "stop" more as an
interrupt signal (with an according "re-start" signal, that wakes up the job
again).
Any other opinions? Maybe we need a voting for the signal name.
> Add "terminate" signal to cleanly stop streaming jobs
> -----------------------------------------------------
>
> Key: FLINK-2111
> URL: https://issues.apache.org/jira/browse/FLINK-2111
> Project: Flink
> Issue Type: Improvement
> Components: Distributed Runtime, JobManager, Local Runtime,
> Streaming, TaskManager, Webfrontend
> Reporter: Matthias J. Sax
> Assignee: Matthias J. Sax
> Priority: Minor
>
> Currently, streaming jobs can only be stopped using "cancel" command, what is
> a "hard" stop with no clean shutdown.
> The new introduced "terminate" signal, will only affect streaming source
> tasks such that the sources can stop emitting data and terminate cleanly,
> resulting in a clean termination of the whole streaming job.
> This feature is a pre-requirment for
> https://issues.apache.org/jira/browse/FLINK-1929
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
