Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: yarn-issues@hadoop.apache.org
Date: Mon, 12 May 2014 17:05:16 +0000 (UTC)
From: "Karthik Kambatla (JIRA)" <jira@apache.org>
To: yarn-issues@hadoop.apache.org
Message-ID: <JIRA.12676565.1383116589025.330377.1399914316900@arcas>
In-Reply-To: <JIRA.12676565.1383116589025@arcas>
References: <JIRA.12676565.1383116589025@arcas>
Subject: [jira] [Commented] (YARN-1372) Ensure all completed containers are
 reported to the AMs across RM restart
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


    [ https://issues.apache.org/jira/browse/YARN-1372?page=3Dcom.atlassian.=
jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D13995=
247#comment-13995247 ]=20

Karthik Kambatla commented on YARN-1372:
----------------------------------------

Based on offline discussion with Anubhav, Bikas, Jian and Vinod, the contro=
l flow for notifying the AM of finished containers should be as follows:
# NM informs RM and holds on to the information (YARN-1336 should handle th=
is as well)
# RM informs AM
# AM acks RM
# RM acks NM
# NM deletes the information

> Ensure all completed containers are reported to the AMs across RM restart
> -------------------------------------------------------------------------
>
>                 Key: YARN-1372
>                 URL: https://issues.apache.org/jira/browse/YARN-1372
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: resourcemanager
>            Reporter: Bikas Saha
>            Assignee: Anubhav Dhoot
>
> Currently the NM informs the RM about completed containers and then remov=
es those containers from the RM notification list. The RM passes on that co=
mpleted container information to the AM and the AM pulls this data. If the =
RM dies before the AM pulls this data then the AM may not be able to get th=
is information again. To fix this, NM should maintain a separate list of su=
ch completed container notifications sent to the RM. After the AM has pulle=
d the containers from the RM then the RM will inform the NM about it and th=
e NM can remove the completed container from the new list. Upon re-register=
 with the RM (after RM restart) the NM should send the entire list of compl=
eted containers to the RM along with any other containers that completed wh=
ile the RM was dead. This ensures that the RM can inform the AM's about all=
 completed containers. Some container completions may be reported more than=
 once since the AM may have pulled the container but the RM may die before =
notifying the NM about the pull.


--
This message was sent by Atlassian JIRA
(v6.2#6252)