You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@flink.apache.org by "Truong Duc Kien (JIRA)" <ji...@apache.org> on 2018/05/29 09:50:00 UTC

[jira] [Created] (FLINK-9465) Separate timeout for savepoint and checkpoint

Truong Duc Kien created FLINK-9465:
--------------------------------------

             Summary: Separate timeout for savepoint and checkpoint
                 Key: FLINK-9465
                 URL: https://issues.apache.org/jira/browse/FLINK-9465
             Project: Flink
          Issue Type: Improvement
    Affects Versions: 1.5.0
            Reporter: Truong Duc Kien


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)