Gour Saha commented on YARN-5079:

Given that, we are focused on next-gen Slider as per YARN-4692, it is not much 
beneficial for the Slider community to undertake any new feature primarily if 
it needs significant changes on the agent side (with corresponding AM side 
changes). All of such work will be throw away in the new agent-less 

Specifically, SLIDER-1167 is an application packaging detail. With native yarn 
support for services, where we focus on docker containers, we don't really care 
if a docker image has a single simple service or complex multiple services. It 
is up to the application owner to start as many or as few. Upgrade would need a 
new docker image. Hence it will be unlikely that feature request SLIDER-1167 
will be worked on.

New releases for Slider are mostly going to focus on bug fixes and minor 
enhancements (if at all demanded by existing users).

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

To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org

Reply via email to