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 8E28A184BC for ; Wed, 21 Oct 2015 15:23:28 +0000 (UTC) Received: (qmail 79825 invoked by uid 500); 21 Oct 2015 15:23:28 -0000 Delivered-To: apmail-hadoop-yarn-issues-archive@hadoop.apache.org Received: (qmail 79739 invoked by uid 500); 21 Oct 2015 15:23:28 -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 79428 invoked by uid 99); 21 Oct 2015 15:23:28 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 21 Oct 2015 15:23:28 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id D4DD12C044E for ; Wed, 21 Oct 2015 15:23:27 +0000 (UTC) Date: Wed, 21 Oct 2015 15:23:27 +0000 (UTC) From: "winghc (JIRA)" To: yarn-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (YARN-4161) Capacity Scheduler : Assign single or multiple containers per heart beat driven by configuration 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-4161?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14967311#comment-14967311 ] winghc commented on YARN-4161: ------------------------------ we just encountered this problem when we submit large job in our production env. using ambari, which only support capacity scheduler. Any patch there? > Capacity Scheduler : Assign single or multiple containers per heart beat driven by configuration > ------------------------------------------------------------------------------------------------ > > Key: YARN-4161 > URL: https://issues.apache.org/jira/browse/YARN-4161 > Project: Hadoop YARN > Issue Type: New Feature > Components: capacityscheduler > Reporter: Mayank Bansal > Assignee: Mayank Bansal > > Capacity Scheduler right now schedules multiple containers per heart beat if there are more resources available in the node. > This approach works fine however in some cases its not distribute the load across the cluster hence throughput of the cluster suffers. I am adding feature to drive that using configuration by that we can control the number of containers assigned per heart beat. -- This message was sent by Atlassian JIRA (v6.3.4#6332)