Myracle opened a new pull request, #27484:
URL: https://github.com/apache/flink/pull/27484
## What is the purpose of the change
This pull request adds a new configuration option
execution.checkpointing.initial-delay that allows users to configure the delay
before the first checkpoint is triggered after job startup. This is
particularly useful for jobs that need time to warm up or catch up with
backlogs (e.g., consuming from Kafka with large lag) before performing the
first checkpoint.
Currently, the initial delay before the first checkpoint is randomly chosen
between minPauseBetweenCheckpoints and baseInterval. This behavior is not
configurable and may not be suitable for scenarios where jobs need a longer
warm-up period. With this change, users can explicitly configure the initial
delay to avoid checkpoint overhead during the critical catch-up phase.
## Brief change log
- *Added new configuration option execution.checkpointing.initial-delay in
CheckpointingOptions*
- *Extended CheckpointCoordinatorConfiguration to include
initialCheckpointDelay field with builder support*
- *Added getInitialCheckpointDelay() and setInitialCheckpointDelay()
methods to CheckpointConfig*
- *Modified getRandomInitDelay() method in CheckpointCoordinator to use
configured initial delay with small random jitter*
- *Updated StreamGraph to pass the new configuration when building
CheckpointCoordinatorConfiguration*
- *Added documentation for the new configuration option in both English
and Chinese docs*
## Verifying this change
This change added tests and can be verified as follows:
- *Added CheckpointCoordinatorInitialDelayTest with comprehensive unit
tests for the new initial delay feature*
- *Extended CheckpointCoordinatorTriggeringTest *
- *Extended CheckpointConfigFromConfigurationTest to verify the
configuration can be loaded from file and set via API*
## Does this pull request potentially affect one of the following parts:
- Dependencies (does it add or upgrade a dependency): (no)
- The public API, i.e., is any changed class annotated with
`@Public(Evolving)`: (no)
- The serializers: (yes / no / don't know)
- The runtime per-record code paths (performance sensitive): (no)
- Anything that affects deployment or recovery: JobManager (and its
components), Checkpointing, Kubernetes/Yarn, ZooKeeper: (no)
- The S3 file system connector: (no)
## Documentation
- Does this pull request introduce a new feature? (yes)
- If yes, how is the feature documented? (docs / JavaDocs)
--
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]
