You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@beam.apache.org by "Tobias Kaymak (Jira)" <ji...@apache.org> on 2020/04/06 13:18:00 UTC
[jira] [Closed] (BEAM-9423) Re-Add the stop button to the Flink web
interface for pipelines
[ https://issues.apache.org/jira/browse/BEAM-9423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tobias Kaymak closed BEAM-9423.
-------------------------------
Fix Version/s: 2.19.0
2.20.0
Resolution: Not A Problem
> Re-Add the stop button to the Flink web interface for pipelines
> ---------------------------------------------------------------
>
> Key: BEAM-9423
> URL: https://issues.apache.org/jira/browse/BEAM-9423
> Project: Beam
> Issue Type: Bug
> Components: runner-flink
> Affects Versions: 2.19.0, 2.20.0
> Reporter: Tobias Kaymak
> Assignee: Maximilian Michels
> Priority: Major
> Fix For: 2.20.0, 2.19.0
>
> Attachments: Screenshot 2020-04-06 at 11.40.28.png
>
>
> The Flink 1.9/1.10 web interface is missing the Stop button for a streaming pipeline, which is pretty useful to drain a streaming pipeline.
> For example to be able to cleanly shutdown a pipeline when a feature is going to be released tomorrow, and the pipeline processing code should be updated before, without the overhead of re-reading the complete past. Taking a snapshot uses the current representation of the Beam code as a Flink job, but what if one wants to update the Beam code and thus the pipeline code without the need to reprocess the whole history? Moreover, a stop button is very useful when a new Flink version is going to be rolled out: then one can drain all pipelines, rollout a new Flink version and start them at the point where they left off with their last committed offset in Kafka.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)