Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: yarn-issues@hadoop.apache.org
Date: Tue, 2 Sep 2014 19:51:25 +0000 (UTC)
From: "Sangjin Lee (JIRA)" <jira@apache.org>
To: yarn-issues@hadoop.apache.org
Message-ID: <JIRA.12686232.1387841344000.11896.1409687485916@Atlassian.JIRA>
In-Reply-To: <JIRA.12686232.1387841344000@Atlassian.JIRA>
References: <JIRA.12686232.1387841344000@Atlassian.JIRA>
 <JIRA.12686232.1387841344034@arcas>
Subject: [jira] [Updated] (YARN-1530) [Umbrella] Store, manage and serve
 per-framework application-timeline data
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/YARN-1530?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Sangjin Lee updated YARN-1530:
------------------------------
    Attachment: ATS-meet-up-8-28-2014-notes.pdf

Some members of the Hadoop open source community that are involved in the ATS development and others had a community meet-up hosted by Twitter. We had a wide-ranging and free discussions on critical use cases and needs, the current state of ATS and where it is going, and some concerns and feedback on the current design.

We hope that some of those items will be incorporated into this work, and will serve the community better.

I am posting the meeting notes from the meet-up so everyone can view what was discussed. Feedback and comments are welcome. Thanks!

> [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: ATS-meet-up-8-28-2014-notes.pdf, 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.3.4#6332)