You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Timo Walther (Jira)" <ji...@apache.org> on 2021/01/18 09:51:00 UTC
[jira] [Commented] (FLINK-9465) Specify a separate savepoint
timeout option via CLI
[ https://issues.apache.org/jira/browse/FLINK-9465?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17267135#comment-17267135 ]
Timo Walther commented on FLINK-9465:
-------------------------------------
Seems nobody is working on this issue anymore. I marked it as unassigned. There was also a thread on the user@ ML on this topic recently:
https://lists.apache.org/thread.html/rac24855efe372b09b025a1eeb1c8111c9bc8c216265ce94cbf0d3880%40%3Cuser.flink.apache.org%3E
> Specify a separate savepoint timeout option via CLI
> ---------------------------------------------------
>
> Key: FLINK-9465
> URL: https://issues.apache.org/jira/browse/FLINK-9465
> Project: Flink
> Issue Type: Improvement
> Components: Runtime / Checkpointing
> Affects Versions: 1.5.0
> Reporter: Truong Duc Kien
> Priority: Major
> Labels: pull-request-available
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Savepoint can take much longer time to perform than checkpoint, especially with incremental checkpoint enabled. This leads to a couple of troubles:
> * For our job, we currently have to set the checkpoint timeout much large than necessary, otherwise we would be unable to perform savepoint.
> * During rush hour, our cluster would encounter high rate of checkpoint timeout due to backpressure, however we're unable to migrate to a larger configuration, because savepoint also timeout.
> In my opinion, the timeout for savepoint should be configurable separately, both in the config file and as parameter to the savepoint command.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)