Samrat002 opened a new pull request, #27077: URL: https://github.com/apache/flink/pull/27077
## What is the purpose of the change FLIP-461 and [FLINK-35549](https://issues.apache.org/jira/browse/FLINK-35549)[2] support that rescale could be executed after the next completed checkpoint. It greatly reduces the amount of data replay after rescale. In FLIP-461, Adaptive Scheduler waits for the next periodic checkpoint to be triggered. In most scenarios, a more efficient solution might be Adaptive Scheduler actively triggers a Checkpoint after all resources are ready(Technically desire resources are ready). ## Brief change log Todo- Add change log ## Verifying this change Todo: 1. Testing changes in cluster 2. Add validation results and proof 3. Add UT ## Does this pull request potentially affect one of the following parts: - Dependencies (does it add or upgrade a dependency): (yes / no) - The public API, i.e., is any changed class annotated with `@Public(Evolving)`: (yes / no) - The serializers: (yes / no / don't know) - The runtime per-record code paths (performance sensitive): (yes / no / don't know) - Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Kubernetes/Yarn, ZooKeeper: (yes / no / don't know) - The S3 file system connector: (yes / no / don't know) ## Documentation - Does this pull request introduce a new feature? (yes / no) - If yes, how is the feature documented? (not applicable / docs / JavaDocs / not documented) -- 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]
