[
https://issues.apache.org/jira/browse/FLINK-9465?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17423992#comment-17423992
]
Till Rohrmann commented on FLINK-9465:
--------------------------------------
Do you want to add the parameter as a query parameter or make it part of the
body of the http request?
For the changes in the REST api I would stick to how it's done there. Same for
the CLI parameter formatting.
How would you name the parameter in the CLI and REST api?
The places you suggested make change for the introduction of the timeout
parameter.
> 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
> Assignee: Feifan Wang
> Priority: Minor
> Labels: auto-deprioritized-major, 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)
