[
https://issues.apache.org/jira/browse/FLINK-18675?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17163289#comment-17163289
]
Ravi Bhushan Ratnakar commented on FLINK-18675:
-----------------------------------------------
[~klion26] from the attached screenshot, there is also one condition in
checkpoint id 190,191 where checkpoint end to end duration is just below
minimum pause duration however next checkpoint got triggered much early than
the minimum pause duration. what do you think about the root cause of this
issue? is this due to "CheckpointCordinator class, at line number 1512
,scheduleAtFixedRate method is being used."?
> Checkpoint not maintaining minimum pause duration between checkpoints
> ---------------------------------------------------------------------
>
> Key: FLINK-18675
> URL: https://issues.apache.org/jira/browse/FLINK-18675
> Project: Flink
> Issue Type: Bug
> Components: Runtime / Checkpointing
> Affects Versions: 1.11.0
> Environment: !image.png!
> Reporter: Ravi Bhushan Ratnakar
> Priority: Critical
> Attachments: image.png
>
>
> I am running a streaming job with Flink 1.11.0 using kubernetes
> infrastructure. I have configured checkpoint configuration like below
> Interval - 3 minutes
> Minimum pause between checkpoints - 3 minutes
> Checkpoint timeout - 10 minutes
> Checkpointing Mode - Exactly Once
> Number of Concurrent Checkpoint - 1
>
> Other configs
> Time Characteristics - Processing Time
>
> I am observing an usual behaviour. *When a checkpoint completes successfully*
> *and if it's end to end duration is almost equal or greater than Minimum
> pause duration then the next checkpoint gets triggered immediately without
> maintaining the Minimum pause duration*. Kindly notice this behaviour from
> checkpoint id 194 onward in the attached screenshot
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
