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 "Sangjin Lee (JIRA)" <ji...@apache.org> on 2016/04/28 22:54:14 UTC

[jira] [Commented] (YARN-2928) YARN Timeline Service: Next generation

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

Sangjin Lee commented on YARN-2928:
-----------------------------------

For those who are following this ticket, we are nearing the first merge to trunk milestone: http://markmail.org/message/27uk4iwqvihs335e

Please check out the WIP documentation on YARN-3150. Thanks!

> YARN Timeline Service: Next generation
> --------------------------------------
>
>                 Key: YARN-2928
>                 URL: https://issues.apache.org/jira/browse/YARN-2928
>             Project: Hadoop YARN
>          Issue Type: New Feature
>          Components: timelineserver
>            Reporter: Sangjin Lee
>            Assignee: Sangjin Lee
>            Priority: Critical
>         Attachments: ATSv2.rev1.pdf, ATSv2.rev2.pdf, Data model proposal v1.pdf, Timeline Service Next Gen - Planning - ppt.pptx, TimelineServiceStoragePerformanceTestSummaryYARN-2928.pdf
>
>
> We have the application timeline server implemented in yarn per YARN-1530 and YARN-321. Although it is a great feature, we have recognized several critical issues and features that need to be addressed.
> This JIRA proposes the design and implementation changes to address those. This is phase 1 of this effort.



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