[
https://issues.apache.org/jira/browse/FLINK-9465?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16856306#comment-16856306
]
vinoyang commented on FLINK-9465:
---------------------------------
[~kien_truong] About the savepoint timeout config option, I think it would be
better set it through API. Currently, it is configured by
{{CheckpointConfig#setCheckpointTimeout}}. I plan to export the setter of
savepoint's timeout in {{CheckpointConfig}}, then access by
{{StreamExecutionEnvrionment#getCheckpointConfig}} . IMO, the configuration
file in some deployment env (e.g. Standalone) is global for all jobs. In
addition, if we export it through CLI, it will not be conducive to the
consistency of behavior. WDYT?
> 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)
