Return-Path: 
 <user-return-13798-apmail-hadoop-mapreduce-user-archive=hadoop.apache.org@hadoop.apache.org>
X-Original-To: apmail-hadoop-mapreduce-user-archive@minotaur.apache.org
Delivered-To: apmail-hadoop-mapreduce-user-archive@minotaur.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id 8984D10A44
	for <apmail-hadoop-mapreduce-user-archive@minotaur.apache.org>;
 Wed, 19 Feb 2014 19:09:01 +0000 (UTC)
Received: (qmail 55275 invoked by uid 500); 19 Feb 2014 19:08:51 -0000
Delivered-To: apmail-hadoop-mapreduce-user-archive@hadoop.apache.org
Received: (qmail 55163 invoked by uid 500); 19 Feb 2014 19:08:51 -0000
Mailing-List: contact user-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:user-help@hadoop.apache.org>
List-Unsubscribe: <mailto:user-unsubscribe@hadoop.apache.org>
List-Post: <mailto:user@hadoop.apache.org>
List-Id: <user.hadoop.apache.org>
Reply-To: user@hadoop.apache.org
Delivered-To: mailing list user@hadoop.apache.org
Received: (qmail 55153 invoked by uid 99); 19 Feb 2014 19:08:51 -0000
Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136)
    by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 19 Feb 2014 19:08:51 +0000
X-ASF-Spam-Status: No, hits=1.5 required=5.0
	tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS
X-Spam-Check-By: apache.org
Received-SPF: pass (athena.apache.org: domain of anastetsky@spryinc.com
 designates 209.85.212.181 as permitted sender)
Received: from [209.85.212.181] (HELO mail-wi0-f181.google.com)
 (209.85.212.181)
    by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 19 Feb 2014 19:08:44 +0000
Received: by mail-wi0-f181.google.com with SMTP id hi5so972175wib.14
        for <user@hadoop.apache.org>; Wed, 19 Feb 2014 11:08:23 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=1e100.net; s=20130820;
        h=x-gm-message-state:mime-version:date:message-id:subject:from:to
         :content-type;
        bh=huc9BxTSRMcRfdPn9Tmxds4UD38z3CyRWdKVCZ/9I4c=;
        b=fSLa25i4UT/8TAuVJvCRQbQ0AqTjNMozUcT/ghKnMdMdLsbb9DDYiDBZOUn2ObEMMy
         v1oOsGQYfLM0Q5XKtGXnysWH7vyNzpgFIUNjqkBEvljJQxstrZZHqY3El5GZLozF3Fve
         kdc7uIEeIXIhkSHUsYX37jLb02ZvKHO3wme+5LkXi4KPTdF+6G5vnuk9pFvKroyLfb0w
         sscFiG0TaMuB6xdRJPjiLBt7w8TtMqNwMbPTNI2HYDJo9ZHU84QhVEeMNAmczFqoJT6+
         Of0LD453ZueEm1kkn4Ax8OV6IocopiFkxk6z+1MTpea0soTtsyJrxjS5MbkaFsXXDPii
         KFLA==
X-Gm-Message-State: 
 ALoCoQnszn3Gf7Z8jl1eHul790k9KCX5D//my4RITcG4/ZuG6t4pZ2CNLeiLr3nh0PDShUmSgBYJ
MIME-Version: 1.0
X-Received: by 10.180.37.193 with SMTP id a1mr3146822wik.52.1392836902996;
 Wed, 19 Feb 2014 11:08:22 -0800 (PST)
Received: by 10.180.107.133 with HTTP; Wed, 19 Feb 2014 11:08:22 -0800 (PST)
X-Originating-IP: [75.145.94.105]
Date: Wed, 19 Feb 2014 14:08:22 -0500
Message-ID: 
 <CAJDd8GGK9r38nmhZQv0Sun7fRJoEkzj4Cbg0_wZ38Nd6=ops6g@mail.gmail.com>
Subject: Capacity Scheduler capacity vs. maximum-capacity
From: Alex Nastetsky <anastetsky@spryinc.com>
To: user@hadoop.apache.org
Content-Type: multipart/alternative; boundary=e89a8f502fa0d55ee004f2c71c31
X-Virus-Checked: Checked by ClamAV on apache.org

--e89a8f502fa0d55ee004f2c71c31
Content-Type: text/plain; charset=ISO-8859-1

Please help me understand how "capacity" and "maximum-capacity" on a queue
work in the Capacity Scheduler.

My understanding is that a queue is allocated "capacity" amount of
resources, and if it needs more, it can "stretch" up to "maximum-capacity"
resources.

But if that's the case, why do we need "capacity" at all? It seems like
"maximum-capacity" is the true limit and "capacity" is ignored?

Thanks in advance,
Alex.

--e89a8f502fa0d55ee004f2c71c31
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Please help me understand how &quot;capacity&quot; and &qu=
ot;maximum-capacity&quot; on a queue work in the Capacity Scheduler.=A0<div=
><br></div><div>My understanding is that a queue is allocated &quot;capacit=
y&quot; amount of resources, and if it needs more, it can &quot;stretch&quo=
t; up to &quot;maximum-capacity&quot; resources.</div>
<div><br></div><div>But if that&#39;s the case, why do we need &quot;capaci=
ty&quot; at all? It seems like &quot;maximum-capacity&quot; is the true lim=
it and &quot;capacity&quot; is ignored?</div><div><br></div><div>Thanks in =
advance,</div>
<div>Alex.</div></div>

--e89a8f502fa0d55ee004f2c71c31--