[
https://issues.apache.org/jira/browse/YARN-2928?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vrushali C updated YARN-2928:
-----------------------------
Attachment: TimelineServiceStoragePerformanceTestSummaryYARN-2928.pdf
We decided to evaluate two approaches of backend storage implementations in
terms of their performance, scalability, usability, maintenance: YARN-3134
(Phoenix based HBase schema) and YARN-3411 (hybrid HBase schema - vanilla
HBase tables in the direct write path and phoenix based tables for reporting).
Attaching a write-up that describes how we ended up choosing the approach of
writing to vanilla HBase tables (YARN-3411) in the direct write path.
> 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)
