[
https://issues.apache.org/jira/browse/YARN-2928?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14276490#comment-14276490
]
Sangjin Lee commented on YARN-2928:
-----------------------------------
bq. One additional issue for developing the new feature. We may either create a
new sub-module or or reuse the current on: applicationhistoryservice, but put
it into blah.blah.v2 package.
My vote is to start from a clean slate with a new source project (e.g.
"applicationtimelineservice" or some other distinct name) and new packages.
There is a cost of having to copy source into the new project, but it might not
be so bad. That way, it can start clean and small and doesn't have to carry
code that is not relevant. Also, it won't be affected by rebasing.
What do you think?
> Application Timeline Server (ATS) next gen: phase 1
> ---------------------------------------------------
>
> 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
>
>
> 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)
