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 4C7A1200C1A for ; Mon, 13 Feb 2017 13:21:23 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id 4B1C0160B4D; Mon, 13 Feb 2017 12:21:23 +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 9D4A5160B60 for ; Mon, 13 Feb 2017 13:21:22 +0100 (CET) Received: (qmail 11742 invoked by uid 500); 13 Feb 2017 12:19:39 -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 9999 invoked by uid 99); 13 Feb 2017 12:19:36 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 13 Feb 2017 12:19:36 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id DAF1D185856 for ; Mon, 13 Feb 2017 12:19:35 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -1.199 X-Spam-Level: X-Spam-Status: No, score=-1.199 tagged_above=-999 required=6.31 tests=[KAM_ASCII_DIVIDERS=0.8, KAM_LAZY_DOMAIN_SECURITY=1, RP_MATCHES_RCVD=-2.999] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id QB6tmjdioIoV for ; Mon, 13 Feb 2017 12:19:35 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id 5659E610EA for ; Mon, 13 Feb 2017 12:19:13 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id 3C42CE0DE3 for ; Mon, 13 Feb 2017 12:19:05 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id B7E48228EC for ; Mon, 13 Feb 2017 12:10:41 +0000 (UTC) Date: Mon, 13 Feb 2017 12:10:41 +0000 (UTC) From: "Varun Saxena (JIRA)" To: yarn-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Comment Edited] (YARN-6156) AM blacklistdisableThreshold consider node partition count MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Mon, 13 Feb 2017 12:21:23 -0000 [ https://issues.apache.org/jira/browse/YARN-6156?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15863485#comment-15863485 ] Varun Saxena edited comment on YARN-6156 at 2/13/17 12:10 PM: -------------------------------------------------------------- bq. And again AM container is allocated in another non-exclusive node. So we are now +2 from old node count, correct? We should only add this node(i.e. count it towards NM count) and not remove it when AM containers fail then. Will be somewhat difficult to pass. Maybe update it when RMContainer is created or take the label from RMContainer and update it when attempt gets to know about the container. And a similar thing will have to be done in YARN-6148 if we do consider non exclusive labels this way. was (Author: varun_saxena): bq. And again AM container is allocated in another non-exclusive node. So we are now +2 from old node count, correct? We should only add this node(i.e. count it towards NM count) and not remove it when AM containers fail then. Will be somewhat difficult to pass. Maybe update it when RMContainer is created. And a similar thing will have to be done in YARN-6148 if we do consider non exclusive labels this way. > AM blacklistdisableThreshold consider node partition count > ----------------------------------------------------------- > > Key: YARN-6156 > URL: https://issues.apache.org/jira/browse/YARN-6156 > Project: Hadoop YARN > Issue Type: Sub-task > Reporter: Bibin A Chundatt > Assignee: Bibin A Chundatt > Attachments: YARN-6156.0001.patch, YARN-6156.0002.patch > > > As per the current implementation for AM blacklisting disabling is based on completed custer resource. > Incase of partitioned cluster, nodes applicable for AM labels only should be considered as total nodes. -- This message was sent by Atlassian JIRA (v6.3.15#6346) --------------------------------------------------------------------- To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org For additional commands, e-mail: yarn-issues-help@hadoop.apache.org