[
https://issues.apache.org/jira/browse/MAPREDUCE-5858?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14106510#comment-14106510
]
Zhijie Shen commented on MAPREDUCE-5858:
----------------------------------------
[~jeagles], thanks for your feedback, which is useful suggestion. If you have
an more detailed design doc, please share with the community.
As JHS has lived for a long time, we should rebase it on the timeline server
gradually. IMHO, the first step is to make the MR job not only write the
history events to the history files on HDFS, but also publish them to the
timeline server, and it is configurable whether the MR job should write history
files or upload timeline data.
Once this is done, we can make JHS have the option to source the timeline
server for MR jobs' history information, while we preserve the web front. Again
it is the configurable to choose the data source.
Once the data layer is stable, we can further think about migrating the UI. We
can either build web UI on the third-party tool (such as Ambari) or even create
web UI plugin in the timeline server. Any thoughts?
> [Umbrella] MR should make use of the timeline server
> ----------------------------------------------------
>
> Key: MAPREDUCE-5858
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-5858
> Project: Hadoop Map/Reduce
> Issue Type: Task
> Reporter: Zhijie Shen
>
> Now MR relies on its own JobHistoryServer for MR specific history
> information. Given the timeline server is ready, we should gradually migrate
> MR historic data to it as well. relieving MR from maintaining its own history
> server daemon.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
