[
https://issues.apache.org/jira/browse/YARN-321?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13706654#comment-13706654
]
Vinod Kumar Vavilapalli commented on YARN-321:
----------------------------------------------
Like I mentioned:
bq. Querying list of apps based on user-name, queue-name etc. To start with, we
will imitate what JHS does, throw up list of all apps and do the filtering
client side. But we need a better server side solution.
So for both the CLI and web UI, we will start with a client side basic
filtering, perhaps coupled with paging on the results. More advanced analytics
needs a more robust server side solution. I can already imagine file-based
indices, but a more query friendly storage will be needed - a table view via
HCat/HBase over HDFS will be a good start.
> 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
>
> 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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
