You are viewing a plain text version of this content. The canonical link for it is here.
Posted to yarn-issues@hadoop.apache.org by "Junping Du (JIRA)" <ji...@apache.org> on 2014/08/04 15:52:13 UTC
[jira] [Commented] (YARN-2033) Investigate merging generic-history
into the Timeline Store
[ https://issues.apache.org/jira/browse/YARN-2033?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14084670#comment-14084670 ]
Junping Du commented on YARN-2033:
----------------------------------
Thanks [~zjshen] for uploading a proposal and keep updating patches!
The proposal sounds like a good direction. I just take a glance at latest patch which looks pretty big for me and mix of code refactor (move location of TimelineClient, etc.), side logic like: adding originalURL to ApplicationAttemptReport, etc. Can we break this patch to several pieces and create a sub JIRA for each one? That should be much easier for review.
> 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.2.patch, YARN-2033.3.patch, YARN-2033.4.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.2#6252)