[
https://issues.apache.org/jira/browse/FLINK-964?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14054821#comment-14054821
]
Markus Holzemer commented on FLINK-964:
---------------------------------------
I talked to [~JonathanH5] shortly about how to integrate the information in the
jobmanager. I think we should take a similiar approach as how the
EventCollector currently passes its events to the webinterface.
We have this thing called MemoryArchivist that registers itself at the
EventCollector and then gets all events forwarded to store them and make them
available to the webinterface.
I think we can do a similar thing with the profiler. I had a short look at the
code and if I understand it correctly, currently profil information is send via
RPC to the JobManagerProfilerImpl.reportProfilingData(). If we register the
MemoryArchivest at the JobManagerProfiler, profiling information can be
forwarded to it and stored there.
> Integrate profiling code with web interface
> -------------------------------------------
>
> Key: FLINK-964
> URL: https://issues.apache.org/jira/browse/FLINK-964
> Project: Flink
> Issue Type: Improvement
> 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)
