hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Naganarasimha G R (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:26:12 GMT

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

Naganarasimha G R commented on YARN-3166:
-----------------------------------------

Hi [~zjshen] & [~sjlee0]
bq. I'm not aware that RM has something similar to NM aux service to decouple RM and aggregator,
too.
+1 for this approach, even i was thinking in the same lines and actually i had raised jira
for AUX support in RM for some other functionality in YARN - 2267. 

bq. 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?
One problem i can think of,  as per Sangjin's comments still we remove ATSV1 we need to support
both to work <based on configurations enable either of one>. In such a scenario if we
try to Reuse REST then we might end up with lot of If else...

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