You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "vinoyang (JIRA)" <ji...@apache.org> on 2019/06/05 12:38:00 UTC
[jira] [Issue Comment Deleted] (FLINK-9465) Separate timeout for
savepoint and checkpoint
[ https://issues.apache.org/jira/browse/FLINK-9465?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
vinoyang updated FLINK-9465:
----------------------------
Comment: was deleted
(was: You mean we only need to specify the timeout via CLI? we do not need to give a config option via API in {{CheckpointConfig}}?)
> Separate timeout for savepoint and checkpoint
> ---------------------------------------------
>
> 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
> Assignee: vinoyang
> Priority: Major
>
> 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
(v7.6.3#76005)