chenzihao5 opened a new pull request, #30062:
URL: https://github.com/apache/flink/pull/30062
## What is the purpose of the change
In LAZY mode, a request for the details of a job that belongs to an
application returned 404 immediately instead of waiting for the archive to be
loaded. This pull request makes both archive fetchers share the lazy fetch
tasks so that the handler can wait for and prioritize any pending task,
regardless of which fetcher scheduled it.
## Brief change log
- Extract the lazy fetch executors and in-flight task maps into a new
LazyFetchTaskRegistry
- HistoryServer creates the registry once and passes it to both archive
fetchers
## Verifying this change
This change added tests and can be verified as follows:
- Added
AbstractHistoryServerHandlerTest#testLazyModeLoadResourceForApplicationJob,
which blocks the asynchronous detail write of a job inside an application and
asserts that a request for its details waits instead of returning 404. Runs
against both FILE and ROCKSDB storage
- Added
HistoryServerApplicationArchiveFetcherTest#testLazyFetchTasksAreSharedWithJobFetcher,
which asserts that a task scheduled by the application fetcher is visible to
the job fetcher
## 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: no
- 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? no
---
##### Was generative AI tooling used to co-author this PR?
- [X] Yes (please specify the tool below)
Co-authored-by: Claude-Opus-5
--
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]