hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Zhijie Shen (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-3166) [Source organization] Decide detailed package structures for timeline service v2 components
Date Thu, 19 Feb 2015 23:46:12 GMT

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

Zhijie Shen commented on YARN-3166:
-----------------------------------

1. If YARN-3087 can be resolved, we can probably make NM avoid the dependency on the timeline
service module.

2. I'm not aware that RM has something similar to NM aux service to decouple RM and aggregator,
too. It seems to be more elegant to have base-aggregator or server-oriented interfaces in
server-common, but I okay with both. In addition to packaging, coupling with RM means that
we cannot deploy RM aggregator with different versions of RM.

3. We can add the method to operate the new data model into the existing client class, instead
of creating a new one. The benefit is that we can reuse the whole skeleton, including http
rest wrapper, security and retry code, but just need to handle some different data objects,
and direct the request to a different location. Instead of deprecate the whole class, we can
deprecate the individual methods. Thought?

> [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