[
https://issues.apache.org/jira/browse/YARN-1564?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14527257#comment-14527257
]
Steve Loughran commented on YARN-1564:
--------------------------------------
They're mostly unrelated; here are some composite services that extend the
single CompositeService with
# ability of other bits of code to add children
# policy that if one child stops/fails then the service itself does
# sequential container that starts one after the other
# one that execs things
It's things we use in Slider to actually construct the internals of our app; AM
comes up & creates a composite to hold all its children, can exec things
locally/async to do some work. And we subclass some for other features; the app
itself becomes an aggregation of services with a unified lifecycle. (e.g IPC
service, Web yarn service, Metrics & Monitoring, TimelineClient)
Where ATS integration would benefit is in
(a) potentially having a service listen to lifecycle events and automatically
publish them
(b) the YARN-679 entry point, which will provide a single, robust, entry point
to instantiate anything that implements Service, and, if they add the entry
point, better passdown of commands
> add some basic workflow YARN services
> -------------------------------------
>
> Key: YARN-1564
> URL: https://issues.apache.org/jira/browse/YARN-1564
> Project: Hadoop YARN
> Issue Type: New Feature
> Components: api
> Affects Versions: 2.4.0
> Reporter: Steve Loughran
> Assignee: Steve Loughran
> Priority: Minor
> Attachments: YARN-1564-001.patch
>
> Original Estimate: 24h
> Time Spent: 48h
> Remaining Estimate: 0h
>
> I've been using some alternative composite services to help build workflows
> of process execution in a YARN AM.
> They and their tests could be moved in YARN for the use by others -this would
> make it easier to build aggregate services in an AM
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
