Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: yarn-issues@hadoop.apache.org
Date: Tue, 30 Sep 2014 22:21:34 +0000 (UTC)
From: "Jian He (JIRA)" <jira@apache.org>
To: yarn-issues@hadoop.apache.org
Message-ID: <JIRA.12745093.1412115512000.159341.1412115694933@Atlassian.JIRA>
In-Reply-To: <JIRA.12745093.1412115512000@Atlassian.JIRA>
References: <JIRA.12745093.1412115512000@Atlassian.JIRA>
 <JIRA.12745093.1412115512887@arcas>
Subject: [jira] [Updated] (YARN-2630)
 TestDistributedShell#testDSRestartWithPreviousRunningContainers fails
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Jian He updated YARN-2630:
--------------------------
    Description: The problem is that after YARN-1372, in work-preserving AM restart, the re-launched AM will also receive previously failed AM container. But DistributedShell logic is not expecting this extra completed container.    (was: The problem is that after YARN-1372, the re-launched AM will also receive previously failed AM container. And DistributedShell logic is not expecting this extra completed container.  )

> TestDistributedShell#testDSRestartWithPreviousRunningContainers fails
> ---------------------------------------------------------------------
>
>                 Key: YARN-2630
>                 URL: https://issues.apache.org/jira/browse/YARN-2630
>             Project: Hadoop YARN
>          Issue Type: Bug
>            Reporter: Jian He
>            Assignee: Jian He
>
> The problem is that after YARN-1372, in work-preserving AM restart, the re-launched AM will also receive previously failed AM container. But DistributedShell logic is not expecting this extra completed container.  


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