hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Junping Du (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (YARN-2033) Investigate merging generic-history into the Timeline Store
Date Thu, 11 Sep 2014 13:46:35 GMT

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

Junping Du updated YARN-2033:
-----------------------------
    Attachment: YARN-2033.13.patch

The .12 patch cannot apply anymore due to conflict with latest changes on trunk. Rebase the
patch to latest trunk branch and do slightly update in .13. Committing it pending on Jenkins'
test.

> Investigate merging generic-history into the Timeline Store
> -----------------------------------------------------------
>
>                 Key: YARN-2033
>                 URL: https://issues.apache.org/jira/browse/YARN-2033
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>            Reporter: Vinod Kumar Vavilapalli
>            Assignee: Zhijie Shen
>         Attachments: ProposalofStoringYARNMetricsintotheTimelineStore.pdf, YARN-2033.1.patch,
YARN-2033.10.patch, YARN-2033.11.patch, YARN-2033.12.patch, YARN-2033.13.patch, YARN-2033.2.patch,
YARN-2033.3.patch, YARN-2033.4.patch, YARN-2033.5.patch, YARN-2033.6.patch, YARN-2033.7.patch,
YARN-2033.8.patch, YARN-2033.9.patch, YARN-2033.Prototype.patch, YARN-2033_ALL.1.patch, YARN-2033_ALL.2.patch,
YARN-2033_ALL.3.patch, YARN-2033_ALL.4.patch
>
>
> Having two different stores isn't amicable to generic insights on what's happening with
applications. This is to investigate porting generic-history into the Timeline Store.
> One goal is to try and retain most of the client side interfaces as close to what we
have today.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message