[
https://issues.apache.org/jira/browse/YARN-5079?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15282987#comment-15282987
]
Karthik Kambatla commented on YARN-5079:
----------------------------------------
I agree with Hitesh. The mailing list might be more conducive for discussion.
On the surface, this definitely seems like a good idea. It would be nice to
understand the details a little better:
# For folks who don't know Slider all that well, it would help to enumerate the
components of Slider and a super brief description of what they do.
# What parts among these are being proposed for a merge?
# What happens to the rest of the parts? Continue to live in Slider? Is the
slider community comfortable with that? From the thread Gour pointed to, app
packages seem like something that need more discussion.
# What release would we target for a Yarn-ified release of said Slider
components? Hadoop 3?
# How do we propose to accommodate Slider committers and PMC members, who are
not committers/PMC members on Yarn?
# With respect to CLI and UIs, how flexible is Slider and the Slider community
with homogenizing with Yarn where applicable. I doubt if we have a lot of this,
but would be good to discuss.
> [Umbrella] Native YARN framework layer for services and beyond
> --------------------------------------------------------------
>
> Key: YARN-5079
> URL: https://issues.apache.org/jira/browse/YARN-5079
> Project: Hadoop YARN
> Issue Type: New Feature
> Reporter: Vinod Kumar Vavilapalli
> Assignee: Vinod Kumar Vavilapalli
>
> (See overview doc at YARN-4692, modifying and copy-pasting some of the
> relevant pieces and sub-section 3.3.1 to track the specific sub-item.)
> (This is a companion to YARN-4793 in our effort to simplify the entire story,
> but focusing on APIs)
> So far, YARN by design has restricted itself to having a very low-level API
> that can support any type of application. Frameworks like Apache Hadoop
> MapReduce, Apache Tez, Apache Spark, Apache REEF, Apache Twill, Apache Helix
> and others ended up exposing higher level APIs that end-users can directly
> leverage to build their applications on top of YARN. On the services side,
> Apache Slider has done something similar.
> With our current attention on making services first-class and simplified,
> it's time to take a fresh look at how we can make Apache Hadoop YARN support
> services well out of the box. Beyond the functionality that I outlined in the
> previous sections in the doc on how NodeManagers can be enhanced to help
> services, the biggest missing piece is the framework itself. There is a lot
> of very important functionality that a services' framework can own together
> with YARN in executing services end-to-end.
> In this JIRA I propose we look at having a native Apache Hadoop framework for
> running services natively on YARN.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
