[
https://issues.apache.org/jira/browse/FLINK-964?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14069244#comment-14069244
]
Daniel Warneke commented on FLINK-964:
--------------------------------------
Hi Jonathan,
sorry for my late response.
In order to learn about the completion of a job, you need to subscribe to the
job events and look out for JobStatus.FINISHED, JobStatus.CANCELED or
JobStatus.FAILED. The JobManagerProfilerImpl does not know about the job
status. The best way to retrieve all the relevent data at once is through the
event collector.
This in-memory job archive is new to me. I don't know who introduced it and I'm
not sure if it is a good design in the long run. YARN outsourced such an
archive from its central ResourceManager process to a separate JobHistoryServer
process because before a growing archive could introduce out-of-memory
situations and cause an entire cluster outage.
> Integrate profiling code with web interface
> -------------------------------------------
>
> Key: FLINK-964
> URL: https://issues.apache.org/jira/browse/FLINK-964
> Project: Flink
> Issue Type: Improvement
> Components: Local Runtime, Webfrontend
> Affects Versions: 0.6-incubating
> Reporter: Stephan Ewen
> Assignee: Jonathan Hasenburg
>
> This issue is subject to discussion.
> The profiling code currently needs to be kept in sync with the job graph
> code, execution graph code, and runtime code.
> Since that part of the code is undergoing quite some changes and the
> profiling code is not used right now, I suggest to remove it, or move it to
> an artifact repository.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
