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) [Source organization] Decide detailed package structures for timeline service v2 components
Date Fri, 20 Feb 2015 19:52:12 GMT

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

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

Hello guys, sorry for the late reply...

bq. RM and NM modules will depend on timeline service module?
I agree that for RM, this is almost unavoidable. I think it's reasonable to let RM/NMs (in
future) depend on timeline services, but we need to be careful on cyclic dependencies? 

bq. What is the difference between TimelineStorage and TimelineStorageImpl?
We may need some renaming here. In my original thought, TimelineStorage class translates operations
based on our object model to data storage layer method calls. These methods should be implemented
by a TimelineStorageImpl object (and its subclasses, of course). 

> [Source organization] 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