chenzihao created FLINK-41601:
---------------------------------
Summary: HistoryServer in LAZY mode returns 404 for job details of
jobs that belong to an application
Key: FLINK-41601
URL: https://issues.apache.org/jira/browse/FLINK-41601
Project: Flink
Issue Type: Bug
Components: Runtime / Web Frontend
Reporter: chenzihao
As mentioned in https://issues.apache.org/jira/browse/FLINK-41286.
Opening a not-yet-downloaded job: does not behave as documented for jobs that
have an application ID (FILE storage).
GET /jobs/<id>/vertices/<vid> right after start returns 404 within 3-19 ms
instead of waiting; the same request succeeds only after the background task
finishes the job (about 46-89 s here).
The same archives copied to <dir>/<jobId> (no application ID) wait 50-58 s and
return 200, as the FLIP describes.
Cause:
AbstractHistoryServerHandler#loadResource (lines 339-354) asks only the job
HistoryServerArchiveFetcher (needLazyLoadIndividually,
waitLazyFetchArchiveFinished).
Jobs with an application ID are scheduled by
HistoryServerApplicationArchiveFetcher, which keeps the task in its own map, so
the handler finds nothing to wait for or to prioritize.
--
This message was sent by Atlassian Jira
(v10.3.26#10030026)