Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: yarn-issues@hadoop.apache.org
Date: Sat, 13 Feb 2016 23:15:18 +0000 (UTC)
From: "Arun Suresh (JIRA)" <jira@apache.org>
To: yarn-issues@hadoop.apache.org
Message-ID: <JIRA.12938931.1455311745000.47817.1455405318322@Atlassian.JIRA>
In-Reply-To: <JIRA.12938931.1455311745000@Atlassian.JIRA>
References: <JIRA.12938931.1455311745000@Atlassian.JIRA>
 <JIRA.12938931.1455311745266@arcas>
Subject: [jira] [Commented] (YARN-4692) [Umbrella] Simplified and
 first-class support for services in YARN
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


    [ https://issues.apache.org/jira/browse/YARN-4692?page=3Dcom.atlassian.=
jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D15146=
246#comment-15146246 ]=20

Arun Suresh commented on YARN-4692:
-----------------------------------

Missed adding this to my previous comment:

# Container Auto-Scaling:=20
Someway to allow user to specify rules like "Add/Remove Container for role =
if *mem*/*iops*/*cpu per container* exceeds/goes below threshold=E2=80=9D w=
hen launching an LR App. We can probably design a rule specification that c=
an be consumed by the service or else we can probably provide Interface hoo=
ks that can be extended/implemented by the end user and packaged with the A=
pp.

> [Umbrella] Simplified and first-class support for services in YARN
> ------------------------------------------------------------------
>
>                 Key: YARN-4692
>                 URL: https://issues.apache.org/jira/browse/YARN-4692
>             Project: Hadoop YARN
>          Issue Type: New Feature
>            Reporter: Vinod Kumar Vavilapalli
>            Assignee: Vinod Kumar Vavilapalli
>         Attachments: YARN-First-Class-And-Simplified-Support-For-Services=
-v0.pdf
>
>
> YARN-896 focused on getting the ball rolling on the support for services =
(long running applications) on YARN.
> I=E2=80=99d like propose the next stage of this effort: _Simplified and f=
irst-class support for services in YARN_.
> The chief rationale for filing a separate new JIRA is threefold:
>  - Do a fresh survey of all the things that are already implemented in th=
e project
>  - Weave a comprehensive story around what we further need and attempt to=
 rally the community around a concrete end-goal, and
>  - Additionally focus on functionality that YARN-896 and friends left for=
 higher layers to take care of and see how much of that is better integrate=
d into the YARN platform itself.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)