You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2015/07/10 15:17:04 UTC
[jira] [Commented] (FLINK-2111) Add "stop" signal to cleanly
shutdown streaming jobs
[ https://issues.apache.org/jira/browse/FLINK-2111?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14622264#comment-14622264 ]
ASF GitHub Bot commented on FLINK-2111:
---------------------------------------
Github user mjsax commented on the pull request:
https://github.com/apache/flink/pull/750#issuecomment-120408249
Changes applied:
- renamed signal name from TERMINATE to STOP (as decided by community vote)
- reverted changes to execution graph state machine
- added interface `Stopable` an reverted method `AbstractInvocable.stop()`
- added `JobType` enum (Batching / Streaming) [as discussed at last Meetup with @StephanEwen ]
- extended test coverage
Please review again.
> Add "stop" signal to cleanly shutdown 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 "stop" signal, will only affect streaming source tasks such that the sources can stop emitting data and shutdown cleanly, resulting in a clean shutdown 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)