Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Date: Thu, 26 May 2016 16:16:13 +0000 (UTC)
From: "Vinod Kumar Vavilapalli (JIRA)" <jira@apache.org>
To: yarn-issues@hadoop.apache.org
Message-ID: <JIRA.12969402.1463089544000.304520.1464279373066@Atlassian.JIRA>
In-Reply-To: <JIRA.12969402.1463089544000@Atlassian.JIRA>
References: <JIRA.12969402.1463089544000@Atlassian.JIRA> <JIRA.12969402.1463089544343@arcas>
Subject: [jira] [Commented] (YARN-5079) [Umbrella] Native YARN framework
 layer for services and beyond
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
archived-at: Thu, 26 May 2016 16:16:14 -0000


    [ https://issues.apache.org/jira/browse/YARN-5079?page=3Dcom.atlassian.=
jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D15302=
325#comment-15302325 ]=20

Vinod Kumar Vavilapalli commented on YARN-5079:
-----------------------------------------------

[~kasha]
bq. The mailing list might be more conducive for discussion.=20
bq. How do we propose to accommodate Slider committers and PMC members, who=
 are not committers/PMC members on Yarn?
Agreed, I just wanted us to wrap up top-level technical discussions here an=
d bring it to some shape so that we can take the rest of the open issues co=
mmunity related discussions to the mailing list.

[~gsaha]
{quote}
One way to do this, is by:
a. Create a branch in Hadoop and move Slider AM, Client and tests into it
b. Create a branch in Slider which will have only Agent and App-Packages an=
d will point to Slider core (AM and Client) as Hadoop modules
{quote}
This is the most practical way forward, +1.

bq. It is likely that we start, by contributing this code into a branch in =
Hadoop and then work on an Agent-less or thin-Agent architecture. Subsequen=
tly, we can include this in one of the early Hadoop-3 releases.
+1 again.

> [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 re=
levant 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 st=
ory, but focusing on APIs)
> So far, YARN by design has restricted itself to having a very low-=C2=ADl=
evel API that can support any type of application. Frameworks like Apache H=
adoop MapReduce, Apache Tez, Apache Spark, Apache REEF, Apache Twill, Apach=
e Helix and others ended up exposing higher level APIs that end=C2=AD-users=
 can directly leverage to build their applications on top of YARN. On the s=
ervices side, Apache Slider has done something similar.
> With our current attention on making services first=C2=AD-class and simpl=
ified, 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 outl=
ined in the previous sections in the doc on how NodeManagers can be enhance=
d to help services, the biggest missing piece is the framework itself. Ther=
e is a lot of very important functionality that a services' framework can o=
wn together with YARN in executing services end=C2=AD-to=C2=AD-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: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org