Return-Path: X-Original-To: apmail-hadoop-yarn-issues-archive@minotaur.apache.org Delivered-To: apmail-hadoop-yarn-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 7D139188D8 for ; Fri, 5 Feb 2016 04:20:40 +0000 (UTC) Received: (qmail 57491 invoked by uid 500); 5 Feb 2016 04:20:40 -0000 Delivered-To: apmail-hadoop-yarn-issues-archive@hadoop.apache.org Received: (qmail 57417 invoked by uid 500); 5 Feb 2016 04:20:40 -0000 Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: yarn-issues@hadoop.apache.org Delivered-To: mailing list yarn-issues@hadoop.apache.org Received: (qmail 57064 invoked by uid 99); 5 Feb 2016 04:20:40 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 05 Feb 2016 04:20:40 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id E9B7C2C1F64 for ; Fri, 5 Feb 2016 04:20:39 +0000 (UTC) Date: Fri, 5 Feb 2016 04:20:39 +0000 (UTC) From: "sandflee (JIRA)" To: yarn-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (YARN-4138) Roll back container resource allocation after resource increase token expires MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/YARN-4138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15133627#comment-15133627 ] sandflee commented on YARN-4138: -------------------------------- Hi, [~mding], there may some cases not user/app error, 1, increase resource from 1G to 5G 2, get a 5G token and send it to NM 3, before container increased msg come to RM, AM decrease resource from 5G -> 4G, (last confirmed is 1G) 4, container increase msg come to RM, in current logic, we don't confirm it, just send a decrease msg to NM 5, container increase timer expire, the resource is rolled back to 1G in 4, maybe We could set lastConfirmed to 4G. > Roll back container resource allocation after resource increase token expires > ----------------------------------------------------------------------------- > > Key: YARN-4138 > URL: https://issues.apache.org/jira/browse/YARN-4138 > Project: Hadoop YARN > Issue Type: Sub-task > Components: api, nodemanager, resourcemanager > Reporter: MENG DING > Assignee: MENG DING > Attachments: YARN-4138-YARN-1197.1.patch, YARN-4138-YARN-1197.2.patch, YARN-4138.3.patch, YARN-4138.4.patch, YARN-4138.5.patch > > > In YARN-1651, after container resource increase token expires, the running container is killed. > This ticket will change the behavior such that when a container resource increase token expires, the resource allocation of the container will be reverted back to the value before the increase. -- This message was sent by Atlassian JIRA (v6.3.4#6332)