Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Date: Thu, 22 Sep 2016 04:56:20 +0000 (UTC)
From: "Arun Suresh (JIRA)" <jira@apache.org>
To: yarn-issues@hadoop.apache.org
Message-ID: <JIRA.13001856.1472686616000.634436.1474520180884@Atlassian.JIRA>
In-Reply-To: <JIRA.13001856.1472686616000@Atlassian.JIRA>
References: <JIRA.13001856.1472686616000@Atlassian.JIRA> <JIRA.13001856.1472686616780@arcas>
Subject: [jira] [Commented] (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: Thu, 22 Sep 2016 04:56:27 -0000


    [ https://issues.apache.org/jira/browse/YARN-5609?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15512144#comment-15512144 ] 

Arun Suresh commented on YARN-5609:
-----------------------------------

bq. during rollback, we should not merge the current resourceSet with new one.. it should just be replaced
Oops.. I meant _restart_ instead of _rollback_. in the case of a restart (if there exists a rollback state when the restart is called), both old and new Launch contexts are non-null, so in v006, it used to merge it.. now it doesnt. I know the {{isRollback}} boolean is not really needed... but I thought it makes the code clearer..

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