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 95B6D200B81 for ; Tue, 30 Aug 2016 00:46:22 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 93F55160AB8; Mon, 29 Aug 2016 22:46: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 DC77F160AC8 for ; Tue, 30 Aug 2016 00:46:21 +0200 (CEST) Received: (qmail 97596 invoked by uid 500); 29 Aug 2016 22:46:21 -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 97395 invoked by uid 99); 29 Aug 2016 22:46:20 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 29 Aug 2016 22:46:20 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id D23982C015C for ; Mon, 29 Aug 2016 22:46:20 +0000 (UTC) Date: Mon, 29 Aug 2016 22:46:20 +0000 (UTC) From: "Arun Suresh (JIRA)" To: yarn-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (YARN-5221) Expose UpdateResourceRequest API to allow AM to request for change in container properties MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Mon, 29 Aug 2016 22:46:22 -0000 [ https://issues.apache.org/jira/browse/YARN-5221?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun Suresh updated YARN-5221: ------------------------------ Attachment: YARN-5221.011.patch Updating patch based on [~subru]'s and [~leftnoteasy]'s suggestions. bq. Not sure if the change will cause stored data compability issues while doing rolling upgrade. (New NM read old data) So new NM will be able to read old data.. but not the other way around. bq. Lots of unnecessary formatting changes, is it possible to revert these changes? Actually many of the formatting changes are due to fixing the existing code to the correct code-style :) If you dont mind, can we keep this as it is, since rolling that back to the wrong code style is a bit difficult... > Expose UpdateResourceRequest API to allow AM to request for change in container properties > ------------------------------------------------------------------------------------------ > > Key: YARN-5221 > URL: https://issues.apache.org/jira/browse/YARN-5221 > Project: Hadoop YARN > Issue Type: Bug > Reporter: Arun Suresh > Assignee: Arun Suresh > Attachments: YARN-5221.001.patch, YARN-5221.002.patch, YARN-5221.003.patch, YARN-5221.004.patch, YARN-5221.005.patch, YARN-5221.006.patch, YARN-5221.007.patch, YARN-5221.008.patch, YARN-5221.009.patch, YARN-5221.010.patch, YARN-5221.011.patch > > > YARN-1197 introduced APIs to allow an AM to request for Increase and Decrease of Container Resources after initial allocation. > YARN-5085 proposes to allow an AM to request for a change of Container ExecutionType. > This JIRA proposes to unify both of the above into an Update Container API. -- 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