[
https://issues.apache.org/jira/browse/YARN-1530?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13903621#comment-13903621
]
Zhijie Shen commented on YARN-1530:
-----------------------------------
bq. 1. Be able to represent our events in JSON and hook into whatever source
the user has set up for ingestion (flume, HDFS, etc).
Currently, you can either compose your JSON content and send HTTP request
yourself, or make use of ATSClient and ATSXXXX POJO classes (the names may be
refactored). The latter way should be comparably easier. If the communication
media is changed in the future, we're going to provide relevant user lib to
publish data easily.
bq. Is that the main idea?
Yes, I think so. We want to relieve developers from building a history server
from nothing. Let YARN to provide the infrastructure for generic applications,
and each application focuses on the its individual logic, such as the data
model, and how to render the data.
> [Umbrella] Store, manage and serve per-framework application-timeline data
> --------------------------------------------------------------------------
>
> Key: YARN-1530
> URL: https://issues.apache.org/jira/browse/YARN-1530
> Project: Hadoop YARN
> Issue Type: Bug
> Reporter: Vinod Kumar Vavilapalli
> Attachments: application timeline design-20140108.pdf, application
> timeline design-20140116.pdf, application timeline design-20140130.pdf,
> application timeline design-20140210.pdf
>
>
> This is a sibling JIRA for YARN-321.
> Today, each application/framework has to do store, and serve per-framework
> data all by itself as YARN doesn't have a common solution. This JIRA attempts
> to solve the storage, management and serving of per-framework data from
> various applications, both running and finished. The aim is to change YARN to
> collect and store data in a generic manner with plugin points for frameworks
> to do their own thing w.r.t interpretation and serving.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
