[
https://issues.apache.org/jira/browse/MAPREDUCE-5858?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14085166#comment-14085166
]
Jonathan Eagles commented on MAPREDUCE-5858:
--------------------------------------------
[~zjshen], we need to be careful when designing this. In particular, users of
MR job history server will want to:
- Continue using Job history server with no runtime dependency a timeline
server being present
- Enable or disable timeline server from the client side
- automatic or manual pluggable configuration or disabling of an in memory
solution for local mode testing
- minicluster integration
- Allow for history enabled for timeline server and job history server at the
same time
- What to do for the tracking url for different scenarios above
- New MR UI using backing timeline backing store
> [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)
