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 4808318719 for ; Wed, 30 Dec 2015 20:31:50 +0000 (UTC) Received: (qmail 99010 invoked by uid 500); 30 Dec 2015 20:31:50 -0000 Delivered-To: apmail-hadoop-yarn-issues-archive@hadoop.apache.org Received: (qmail 98961 invoked by uid 500); 30 Dec 2015 20:31:50 -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 98919 invoked by uid 99); 30 Dec 2015 20:31:50 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 30 Dec 2015 20:31:50 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id BF5A12C1F69 for ; Wed, 30 Dec 2015 20:31:49 +0000 (UTC) Date: Wed, 30 Dec 2015 20:31:49 +0000 (UTC) From: "Wangda Tan (JIRA)" To: yarn-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (YARN-4495) add a way to tell AM container increase/decrease request is invalid 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-4495?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15075380#comment-15075380 ] Wangda Tan commented on YARN-4495: ---------------------------------- Thanks for investigations, [~sandflee]. I feel we should make this JIRA to be more generic helpful: - Current any issue of regular resource request becomes InvalidResourceRequestException, but AM doesn't know which resource request is failed. Similar to change container resource request. - Some resource request / change container resource request could be rejected after it added to scheduler. (For example, queue's accessible-node-label changed could cause some original valid resource request changes to invalid.) - Maybe we can add a "RejectedResourceRequest" proto to AllocateResponse, and it contains list of rejected regular resource request, and list of increase/decrease container request. Since it is an API change, please expect that more time/discussion required to settle it down. Set target version to 2.9. > add a way to tell AM container increase/decrease request is invalid > ------------------------------------------------------------------- > > Key: YARN-4495 > URL: https://issues.apache.org/jira/browse/YARN-4495 > Project: Hadoop YARN > Issue Type: Improvement > Reporter: sandflee > Attachments: YARN-4495.01.patch > > > now RM may pass InvalidResourceRequestException to AM or just ignore the change request, the former will cause AMRMClientAsync down. and the latter will leave AM waiting for the relay. -- This message was sent by Atlassian JIRA (v6.3.4#6332)