Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: yarn-issues@hadoop.apache.org
Date: Mon, 23 Dec 2013 23:31:50 +0000 (UTC)
From: "Vinod Kumar Vavilapalli (JIRA)" <jira@apache.org>
To: yarn-issues@hadoop.apache.org
Message-ID: <JIRA.12686232.1387841344034.6352.1387841510818@arcas>
In-Reply-To: <JIRA.12686232.1387841344034@arcas>
References: <JIRA.12686232.1387841344034@arcas>
Subject: [jira] [Commented] (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:comment-tabpanel&focusedCommentId=13856016#comment-13856016 ] 

Vinod Kumar Vavilapalli commented on YARN-1530:
-----------------------------------------------

Working on a design doc that explains requirements and the solution space. I hope to push it out soon..

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