[
https://issues.apache.org/jira/browse/FLINK-9598?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-9598:
----------------------------------
Labels: auto-unassigned pull-request-available stale-major (was:
auto-unassigned pull-request-available)
I am the [Flink Jira Bot|https://github.com/apache/flink-jira-bot/] and I help
the community manage its development. I see this issues has been marked as
Major but is unassigned and neither itself nor its Sub-Tasks have been updated
for 30 days. I have gone ahead and added a "stale-major" to the issue". If this
ticket is a Major, please either assign yourself or give an update. Afterwards,
please remove the label or in 7 days the issue will be deprioritized.
> [Checkpoints] The config Minimum Pause Between Checkpoints doesn't work when
> there's a checkpoint failure
> ---------------------------------------------------------------------------------------------------------
>
> Key: FLINK-9598
> URL: https://issues.apache.org/jira/browse/FLINK-9598
> Project: Flink
> Issue Type: Bug
> Components: Runtime / Checkpointing
> Affects Versions: 1.3.2
> Reporter: Prem Santosh
> Priority: Major
> Labels: auto-unassigned, pull-request-available, stale-major
> Attachments: Screen Shot 2018-06-20 at 7.44.10 AM.png
>
>
> We have set the config Minimum Pause Between Checkpoints to be 10 min but
> noticed that when a checkpoint fails (because it timesout before it
> completes) the application immediately starts taking the next checkpoint.
> This basically stalls the application's progress since its always taking
> checkpoints.
> [^Screen Shot 2018-06-20 at 7.44.10 AM.png] is a screenshot of this issue.
> Details:
> * Running Flink-1.3.2 on EMR
> * checkpoint timeout duration: 40 min
> * minimum pause between checkpoints: 10 min
> There is also a [relevant
> thread|http://apache-flink-user-mailing-list-archive.2336050.n4.nabble.com/Having-a-backoff-while-experiencing-checkpointing-failures-td20618.html]
> that I found on the Flink users group.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)