Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Date: Fri, 3 Mar 2017 08:06:45 +0000 (UTC)
From: =?utf-8?Q?=E5=86=AF=E5=81=A5_=28JIRA=29?= <jira@apache.org>
To: yarn-issues@hadoop.apache.org
Message-ID: <JIRA.13047661.1488456257000.52088.1488528405523@Atlassian.JIRA>
In-Reply-To: <JIRA.13047661.1488456257000@Atlassian.JIRA>
References: <JIRA.13047661.1488456257000@Atlassian.JIRA> <JIRA.13047661.1488456257418@jira-lw-us.apache.org>
Subject: [jira] [Commented] (YARN-6268) Container with extra data
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
archived-at: Fri, 03 Mar 2017 08:06:50 -0000


    [ https://issues.apache.org/jira/browse/YARN-6268?page=3Dcom.atlassian.=
jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D15893=
888#comment-15893888 ]=20

=E5=86=AF=E5=81=A5 commented on YARN-6268:
--------------------------

MRAppMaster's solution use request=E2=80=98s Priority to identify container=
's role,  I think that was not graceful, and maybe can't work  in complicat=
ed case.=20
if you  have many kinds of containers to launch,  you need map every contai=
ner to one unique priority .  if we need decide container's running mode by=
 context(eg: we don't know what process to launch before resource request),=
 use priority doesn't work.

> Container with extra data
> -------------------------
>
>                 Key: YARN-6268
>                 URL: https://issues.apache.org/jira/browse/YARN-6268
>             Project: Hadoop YARN
>          Issue Type: New Feature
>          Components: api
>    Affects Versions: 3.0.0-alpha2
>            Reporter: =E5=86=AF=E5=81=A5
>
> implement a container which can take extra data (eg: some data user defin=
e).  so user can do some operation with that


--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

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