[
https://issues.apache.org/jira/browse/FLINK-22805?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-22805:
-----------------------------------
Labels: auto-deprioritized-critical stale-major (was:
auto-deprioritized-critical)
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 60 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.
> Dynamic configuration of Flink checkpoint interval
> --------------------------------------------------
>
> Key: FLINK-22805
> URL: https://issues.apache.org/jira/browse/FLINK-22805
> Project: Flink
> Issue Type: New Feature
> Components: Runtime / Checkpointing
> Affects Versions: 1.13.1
> Reporter: Fu Kai
> Priority: Major
> Labels: auto-deprioritized-critical, stale-major
>
> Flink currently does not support dynamic configuration of checkpoint interval
> on the fly. It's useful for use cases like backfill/cold-start from a stream
> containing whole history.
>
> In the cold-start phase, resources are fully utilized and the back-pressure
> is high for all upstream operators, causing the checkpoint timeout
> constantly. The real production traffic is far less than that and the
> provisioned resource is capable of handling it.
>
> With the dynamic checkpoint interval configuration, the cold-start process
> can be speeded up with less frequent checkpoint interval or even turned off.
> After the process is completed, the checkpoint interval can be updated to
> normal.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
