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 C6F5E18A95 for ; Sun, 27 Dec 2015 20:47:50 +0000 (UTC) Received: (qmail 41372 invoked by uid 500); 27 Dec 2015 20:47:50 -0000 Delivered-To: apmail-hadoop-yarn-issues-archive@hadoop.apache.org Received: (qmail 41324 invoked by uid 500); 27 Dec 2015 20:47: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 41302 invoked by uid 99); 27 Dec 2015 20:47:50 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 27 Dec 2015 20:47:50 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id 57DE92C1F60 for ; Sun, 27 Dec 2015 20:47:50 +0000 (UTC) Date: Sun, 27 Dec 2015 20:47:50 +0000 (UTC) From: "Karthik Kambatla (JIRA)" To: yarn-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (YARN-1011) [Umbrella] Schedule containers based on utilization of currently allocated containers 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-1011?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15072240#comment-15072240 ] Karthik Kambatla commented on YARN-1011: ---------------------------------------- bq. For resource oversubscription enable/disable for individual nodes, I think it's very important since some nodes could be more important than others. Do you think is it fine to add a configuration item to each NM's yarn-site.xml? That is exactly the intent. Let us continue this conversation on YARN-4512. bq. For scheduler-side implementation, instead of modifying individual scheduler, I think we should try to add over-subscription policy to common scheduling layer since it doesn't sounds very related to specific scheduler implementation. Makes sense. Doubt there is any scheduler-specific smarts here. If at all we need to do them separately, it is most likely because our scheduler abstractions are not clean. > [Umbrella] Schedule containers based on utilization of currently allocated containers > ------------------------------------------------------------------------------------- > > Key: YARN-1011 > URL: https://issues.apache.org/jira/browse/YARN-1011 > Project: Hadoop YARN > Issue Type: New Feature > Reporter: Arun C Murthy > Attachments: yarn-1011-design-v0.pdf > > > Currently RM allocates containers and assumes resources allocated are utilized. > RM can, and should, get to a point where it measures utilization of allocated containers and, if appropriate, allocate more (speculative?) containers. -- This message was sent by Atlassian JIRA (v6.3.4#6332)