[
https://issues.apache.org/jira/browse/YARN-3166?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14326823#comment-14326823
]
Li Lu commented on YARN-3166:
-----------------------------
bq. 1. Should we sort out the package for RM and NM code of writing actual
system data through the aggregator?
Yes. We need to decide this along with our current discussion. This will not
block our current work on object model/aggregator wireup/data storage layer,
but will block us when we start to post data through those aggregators.
bq. 2. RM and NM modules will depend on timeline service module?
I assume they will post data through our clients, am I right here?
> [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)
