dpeacock opened a new pull request, #29584: URL: https://github.com/apache/flink/pull/29584
## What and why Addresses [FLINK-41115](https://issues.apache.org/jira/browse/FLINK-41115). We encountered production rescales where AdaptiveScheduler waited **104–127 seconds for a graph-creation worker**, although executing the supplier took about **0.32 seconds**. Thread dumps showed the general JobManager IO workers occupied by checkpoint-file deletion. ## Change Run only background graph construction and state assignment on a JobManager-owned, shared recovery executor. Checkpoint-trigger initialization and cleanup keep their existing IO executor and feedback relationship. Predecessor sequencing, cancellation, state ownership and shutdown ordering are preserved. The fixed recovery pool uses `jobmanager.io-pool.size`, adding up to N shared workers; configuration docs describe this. The queue remains unbounded, and synchronous storage calls inside recovery can still block. No diagnostic logging, dependency, public API signature, serializer, per-record or S3 connector changes. ## Verification Real MiniCluster tests saturate general IO with deletion and verify restored-task progress before releasing it, while new checkpoint initialization still waits. Negative controls detect incorrect routing, lost checkpoint feedback and premature shutdown. Affected runtime/checkpoint suites and core, streaming, Kubernetes and documentation verification pass on Apache master. Configuration documentation was regenerated. - [X] Generative AI tooling used: pi Generated-by: pi 1.4.0 -- 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]
