hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Li Lu (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-3166) Decide detailed package structures for timeline service v2 components
Date Tue, 10 Feb 2015 22:28:12 GMT

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

Li Lu commented on YARN-3166:
-----------------------------

Thanks [~zjshen]! I think this can be a good starting point, and we can further arrange planned
modules under this framework. 

> Decide detailed package structures for timeline service v2 components
> ---------------------------------------------------------------------
>
>                 Key: YARN-3166
>                 URL: https://issues.apache.org/jira/browse/YARN-3166
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>            Reporter: Li Lu
>            Assignee: Li Lu
>
> Open this JIRA to track all discussions on detailed package structures for timeline services
v2. This JIRA is for discussion only.
> For our current timeline service v2 design, aggregator (previously called "writer") implementation
is in hadoop-yarn-server's:
> {{org.apache.hadoop.yarn.server.timelineservice.aggregator}}
> In YARN-2928's design, the next gen ATS reader is also a server. Maybe we want to put
reader related implementations into hadoop-yarn-server's:
> {{org.apache.hadoop.yarn.server.timelineservice.reader}}
> Both readers and aggregators will expose features that may be used by YARN and other
3rd party components, such as aggregator/reader APIs. For those features, maybe we would like
to expose their interfaces to hadoop-yarn-common's {{org.apache.hadoop.yarn.timelineservice}}?

> Let's use this JIRA as a centralized place to track all related discussions. 



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

Mime
View raw message