[
https://issues.apache.org/jira/browse/YARN-321?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13789951#comment-13789951
]
Vinod Kumar Vavilapalli commented on YARN-321:
----------------------------------------------
I assumed this is a well known problem so didn't try to eloborate on the WHY's.
My comment above
(https://issues.apache.org/jira/browse/YARN-321?focusedCommentId=13706553&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13706553)
kind of captures the core design. Though code level design doc isn't there yet.
We are about to wrap up stuff on YARN-321 branch - will post a more
comprehensive doc covering design and implementation details.
In the mean while, if you have specific questions, fire them away.
> 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: 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)
