[
https://issues.apache.org/jira/browse/FLINK-3492?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15197511#comment-15197511
]
ASF GitHub Bot commented on FLINK-3492:
---------------------------------------
Github user zentol commented on the pull request:
https://github.com/apache/flink/pull/1794#issuecomment-197385184
I've revisited this PR:
* ScheduledTrigger remains unchanged
* StreamEecutionEnvironment remains unchanged
* if the minIntervalBetweenCheckpoints is > 0 a different schedule method
is used
* scheduleAtFixedRate() is used when minInterval == 0. This is the current
behaviour, meaning checkpoints can build up if they aren't processed fast enough
* schedule() is used when minInterval > 0. New stuff right here. It
schedules the next checkpoint relative to the completion of the last. So we
just pop the interval as the period in there and are done.
> Allow users to define a min pause between checkpoints
> -----------------------------------------------------
>
> Key: FLINK-3492
> URL: https://issues.apache.org/jira/browse/FLINK-3492
> Project: Flink
> Issue Type: Improvement
> Components: Streaming
> Reporter: Robert Metzger
> Assignee: Chesnay Schepler
>
> FLINK-3051 introduced already a filed in the {{CheckpointConfig}} to specify
> a min pause between checkpoints.
> In high-load situations (big state), jobs might spend their entire time
> creating snapshots, not processing data. With a min pause between
> checkpoints, users can guarantee that there is a certain time-span the system
> can use for doing some actual data processing.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
