[
https://issues.apache.org/jira/browse/YARN-321?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zhijie Shen updated YARN-321:
-----------------------------
Attachment: AHS Diagram.pdf
I created a diagram to demonstrate what was proposed to do. Hopefully it will
help your understanding. Bellow is a summary of the Jiras:
* Reading/Writing Interfaces and their implementations: YARN-925, YARN-934,
YARN-956, YARN-975, YARN-1002
* RM writing history data: YARN-953, YARN-974, YARN-1030
* Web UI and REST APIs: YARN-954, YARN-1023
* Application history protocol (RPC interface): YARN-955, YARN-978, YARN-979,
YARN-1123, YARN-1266
* Internal Protobuf objects for storage: YARN-947, YARN-1066
> Generic application history service
> -----------------------------------
>
> Key: YARN-321
> URL: https://issues.apache.org/jira/browse/YARN-321
> Project: Hadoop YARN
> Issue Type: Improvement
> Reporter: Luke Lu
> Assignee: Vinod Kumar Vavilapalli
> Attachments: AHS Diagram.pdf, HistoryStorageDemo.java
>
>
> The mapreduce job history server currently needs to be deployed as a trusted
> server in sync with the mapreduce runtime. Every new application would need a
> similar application history server. Having to deploy O(T*V) (where T is
> number of type of application, V is number of version of application) trusted
> servers is clearly not scalable.
> Job history storage handling itself is pretty generic: move the logs and
> history data into a particular directory for later serving. Job history data
> is already stored as json (or binary avro). I propose that we create only one
> trusted application history server, which can have a generic UI (display json
> as a tree of strings) as well. Specific application/version can deploy
> untrusted webapps (a la AMs) to query the application history server and
> interpret the json for its specific UI and/or analytics.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
