Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Date: Wed, 21 Sep 2016 09:06:22 +0000 (UTC)
From: "Arun Suresh (JIRA)" <jira@apache.org>
To: yarn-issues@hadoop.apache.org
Message-ID: <JIRA.13001856.1472686616000.624892.1474448782150@Atlassian.JIRA>
In-Reply-To: <JIRA.13001856.1472686616000@Atlassian.JIRA>
References: <JIRA.13001856.1472686616000@Atlassian.JIRA> <JIRA.13001856.1472686616780@arcas>
Subject: [jira] [Updated] (YARN-5609) Expose upgrade and restart API in
 ContainerManagementProtocol
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Wed, 21 Sep 2016 09:06:24 -0000


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

Arun Suresh updated YARN-5609:
------------------------------
    Attachment: YARN-5609.007.patch

Updating Patch based on your suggestions..

bq. But for restart, as the same resources are re-used, we don't need to re-check. So, I guess we need to retain the behavior for rollback ?
Agreed... In the latest patch, the rollback ResourceSet is now a clone of the prev resourceSet, with all the required LocalResources moved back into the pending list. Had to change a few things to get this to work though.. do take a look..

> Expose upgrade and restart API in ContainerManagementProtocol
> -------------------------------------------------------------
>
>                 Key: YARN-5609
>                 URL: https://issues.apache.org/jira/browse/YARN-5609
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>            Reporter: Arun Suresh
>            Assignee: Arun Suresh
>         Attachments: YARN-5609.001.patch, YARN-5609.002.patch, YARN-5609.003.patch, YARN-5609.004.patch, YARN-5609.005.patch, YARN-5609.006.patch, YARN-5609.007.patch
>
>
> YARN-5620 and YARN-5637 allows an AM to explicitly *upgrade* a container with a new launch context and subsequently *rollback* / *commit* the change on the Container. This can also be used to simply *restart* the Container as well. 
> This JIRA proposes to extend the ContainerManagementProtocol with the following API:
> * *reInitializeContainer*
> * *rollbackLastUpgrade*
> * *commitLastUpgrade*
> * *restartContainer*


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