Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Date: Sat, 7 Jan 2017 01:43:58 +0000 (UTC)
From: "Junping Du (JIRA)" <jira@apache.org>
To: yarn-issues@hadoop.apache.org
Message-ID: <JIRA.12659432.1374612689000.674806.1483753438820@Atlassian.JIRA>
In-Reply-To: <JIRA.12659432.1374612689000@Atlassian.JIRA>
References: <JIRA.12659432.1374612689000@Atlassian.JIRA> <JIRA.12659432.1374612689343@arcas>
Subject: [jira] [Updated] (YARN-959) Add ApplicationAttemptId into container
 environment
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Sat, 07 Jan 2017 01:44:00 -0000


     [ https://issues.apache.org/jira/browse/YARN-959?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Junping Du updated YARN-959:
----------------------------
    Target Version/s:   (was: 2.8.0)

> Add ApplicationAttemptId into container environment
> ---------------------------------------------------
>
>                 Key: YARN-959
>                 URL: https://issues.apache.org/jira/browse/YARN-959
>             Project: Hadoop YARN
>          Issue Type: Improvement
>    Affects Versions: 2.1.0-beta, 2.6.0
>            Reporter: Bikas Saha
>            Assignee: Junping Du
>
> Currently, AM's and containers have to read the container id and then derive the application attempt id from it. While its convenient for YARN to tightly couple container id with application attempt id, it is something that should not be exposed to users. Its easy to let users know about their application attempt id via env instead of requiring them to pull it out of the container id.


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