Myracle commented on code in PR #27484: URL: https://github.com/apache/flink/pull/27484#discussion_r2867200089
########## docs/content/docs/deployment/config.md: ########## @@ -158,6 +158,7 @@ You can configure checkpointing directly in code within your Flink job or applic - `execution.checkpointing.dir`: The directory to write checkpoints to. This takes a path URI like *s3://mybucket/flink-app/checkpoints* or *hdfs://namenode:port/flink/checkpoints*. - `execution.checkpointing.savepoint-dir`: The default directory for savepoints. Takes a path URI, similar to `execution.checkpointing.dir`. - `execution.checkpointing.interval`: The base interval setting. To enable checkpointing, you need to set this value larger than 0. + - `execution.checkpointing.initial-delay`: The initial delay before the first checkpoint is triggered. This is useful for jobs that need time to warm up or catch up with backlogs (e.g., consuming from Kafka with large lag). Review Comment: Thanks for the great suggestion! Regarding the dynamic detection — Flink already has execution.checkpointing.interval-during-backlog (introduced via FLINK-32514) which leverages the isProcessingBacklog signal from sources to dynamically adjust the checkpoint interval at runtime. However, initial-delay addresses a complementary use case: it covers the one-time startup delay for scenarios that cannot be detected by the source's backlog signal, such as JIT warm-up, cache population, or state backend initialization. These two options work together rather than replacing each other. For the documentation suggestion, I fully agree — I've updated the docs and the ConfigOption description to document the impact of not using this delay, the trade-offs, and the relationship with interval-during-backlog. Please take a look! -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
