Zhilong Hong created FLINK-24491:
------------------------------------
Summary: ExecutionGraphInfo may not be archived when the
dispatcher terminates
Key: FLINK-24491
URL: https://issues.apache.org/jira/browse/FLINK-24491
Project: Flink
Issue Type: Bug
Components: Runtime / Configuration
Affects Versions: 1.13.2, 1.14.0, 1.15.0
Reporter: Zhilong Hong
Fix For: 1.13.3, 1.15.0, 1.14.1
When a job finishes, its JobManagerRunnerResult will be processed in the
callback of {{Dispatcher#runJob}}. In the callback, ExecutionGraphInfo will be
archived by HistoryServerArchivist asynchronously. However, the
CompletableFuture of the archiving is ignored. The job may be removed before
the archiving is finished. For the batch job running in the per-job/application
mode, the dispatcher will terminate itself once the job is finished. In this
case, ExecutionGraphInfo may not be archived when the dispatcher terminates.
If the ExecutionGraphInfo is lost, users are not able to know whether the batch
job is finished normally or not. They have to refer to the logs for the result.
The session mode is not affected, since the dispatcher won't terminate itself
once the job is finished. The HistoryServerArchivist gets enough time to
archive the ExcutionGraphInfo.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
