Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 697E9200B86 for ; Sun, 18 Sep 2016 10:18:22 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 68278160AC3; Sun, 18 Sep 2016 08:18:22 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id ACA01160AC0 for ; Sun, 18 Sep 2016 10:18:21 +0200 (CEST) Received: (qmail 50143 invoked by uid 500); 18 Sep 2016 08:18:20 -0000 Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list yarn-issues@hadoop.apache.org Received: (qmail 50128 invoked by uid 99); 18 Sep 2016 08:18:20 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 18 Sep 2016 08:18:20 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id 94E8F2C0D5A for ; Sun, 18 Sep 2016 08:18:20 +0000 (UTC) Date: Sun, 18 Sep 2016 08:18:20 +0000 (UTC) From: "Varun Vasudev (JIRA)" To: yarn-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (YARN-5637) Changes in NodeManager to support Container rollback and commit MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Sun, 18 Sep 2016 08:18:22 -0000 [ https://issues.apache.org/jira/browse/YARN-5637?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15500546#comment-15500546 ] Varun Vasudev commented on YARN-5637: ------------------------------------- Thanks for the patch [~asuresh]! My apologies for the delay in responding. The patch looks mostly good to me. The only question I have to around deleting resources as part of the rollback. Let's say you download a new jar as part of the upgrade. When you do a rollback, this jar will be part of the classpath and this could result in the rollback failing(due to class/function not found issues). Is my understanding wrong? I wouldn't hold up the patch for fixing this - we should probably do it in a different JIRA. > Changes in NodeManager to support Container rollback and commit > --------------------------------------------------------------- > > Key: YARN-5637 > URL: https://issues.apache.org/jira/browse/YARN-5637 > Project: Hadoop YARN > Issue Type: Sub-task > Reporter: Arun Suresh > Assignee: Arun Suresh > Attachments: YARN-5637.001.patch, YARN-5637.002.patch, YARN-5637.003.patch, YARN-5637.004.patch, YARN-5637.005.patch, YARN-5637.006.patch, YARN-5637.007.patch > > > YARN-5620 added support for re-initialization of Containers using a new launch Context. > This JIRA proposes to use the above feature to support upgrade and subsequent rollback or commit of the upgrade. -- 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