hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chris Riccomini (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-1530) [Umbrella] Store, manage and serve per-framework application-timeline data
Date Fri, 31 Jan 2014 23:16:20 GMT

    [ https://issues.apache.org/jira/browse/YARN-1530?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13888286#comment-13888286
] 

Chris Riccomini commented on YARN-1530:
---------------------------------------

Had a look at the design doc. I think I'm starting to get it, but I have a couple of questions:

1. Is the expectation that people will be able to use this for INFO, WARN, ERROR type application
logging?
2. Regarding app-specific UIs, is it going to be possible to embed app-specific UIs with YARN's
UI, instead of having to run an app-specific web-ui? There is some mention of JS UIs, but
it's a little unclear whether this would be embedded in YARN, or served from "somewhere" (to
quote the docs. If it's served from the RM (or some other web-ui in YARN), will it be up to
ops to decide which libraries are embedded, or up to 
3. What are the planned "out of the box implementations" for both the storage and transport
layers? REST+LevelDB+HBase? Are Flume and Kafka implementations expected to happen outside
of the YARN project?

> [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
>
>
> 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)

Mime
View raw message