[YARN-3166] [Source organization] Decide detailed package structures for timeline service v2 components

• Type: Sub-task
• Status: Resolved
• Priority: Major
• Resolution: Won't Fix
• Labels: YARN-5355
• Assignee: Li Lu
• Reporter: Li Lu
• Created: 10/Feb/15 21:43
• Updated: 25/Oct/19 20:24
• Resolved: 30/Aug/19 05:53

Description

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.

Issue Links

• blocks: YARN-3210 [Source organization] Refactor timeline collector according to new code organization