Return-Path: X-Original-To: apmail-hadoop-common-user-archive@www.apache.org Delivered-To: apmail-hadoop-common-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 8BC9310686 for ; Fri, 5 Dec 2014 13:42:08 +0000 (UTC) Received: (qmail 41884 invoked by uid 500); 5 Dec 2014 13:42:02 -0000 Delivered-To: apmail-hadoop-common-user-archive@hadoop.apache.org Received: (qmail 41614 invoked by uid 500); 5 Dec 2014 13:42:02 -0000 Mailing-List: contact user-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@hadoop.apache.org Delivered-To: mailing list user@hadoop.apache.org Received: (qmail 40915 invoked by uid 99); 5 Dec 2014 13:42:00 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 05 Dec 2014 13:42:00 +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 (nike.apache.org: domain of chris.mawata@gmail.com designates 209.85.213.181 as permitted sender) Received: from [209.85.213.181] (HELO mail-ig0-f181.google.com) (209.85.213.181) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 05 Dec 2014 13:41:34 +0000 Received: by mail-ig0-f181.google.com with SMTP id l13so757996iga.8 for ; Fri, 05 Dec 2014 05:41:33 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=e8X4QMS4zQ7m2PZvx1/g34bs0SVkS16rqEN9s9NidyQ=; b=h/P4oNuklyeU+gw/0VPzwJs21wMXNi8khfaH6rFneSESneCiT6PSIDuru6KEMQhiqe pXQpQOeVnV8SIIemVAXj4FEpOkXc9qrBhoX5pNWoYKYQs2gCDGlxAigNEB0cfp92je9J ugzg5Od34cIr07sfZZY1F3tJ9E/xlnbov3abAM1I8oc9fDg7IvWMKDGrgSDSrb2RXRe4 crvxqgSbTekfyDzKrXQwuQ0Lp4Ykn670OCV+7vLB2ZJoXL82e8myewVfkicXM5zWEEwS qlqvrKSl2YpLSiyRjFCVKrwouhKguw4Y3s7V4lB1UhLHtsEmclWVDjXj2qpYsrZrDLU1 TVlQ== MIME-Version: 1.0 X-Received: by 10.107.136.92 with SMTP id k89mr14744496iod.43.1417786893346; Fri, 05 Dec 2014 05:41:33 -0800 (PST) Received: by 10.50.225.172 with HTTP; Fri, 5 Dec 2014 05:41:33 -0800 (PST) Date: Fri, 5 Dec 2014 08:41:33 -0500 Message-ID: Subject: When schedulers consider x% of resources what do they mean? From: Chris Mawata To: user@hadoop.apache.org Content-Type: multipart/alternative; boundary=001a113ecad4252ce70509783cc6 X-Virus-Checked: Checked by ClamAV on apache.org --001a113ecad4252ce70509783cc6 Content-Type: text/plain; charset=UTF-8 Hi all, when you divide up resources e.g. on CapacityScheduler or FairScheduler etc., what does x% or resources mean? So, for example, a guranteed 70% meant to indicate you can have up to 70% of the containers clusterwide irrespective of size of container 70% of the containers on each node or should it not be number of containers but sum of heap sizes? Cheers Chris Mawata --001a113ecad4252ce70509783cc6 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Hi all,
=C2=A0 =C2=A0 =C2=A0when you divide up resourc= es e.g. on CapacityScheduler or FairScheduler etc., what does x% or resourc= es mean? So, for example, a guranteed 70% meant to indicate you can have up= to
70% of the containers clusterwide irrespective of size of con= tainer=C2=A0
70% of the containers =C2=A0on each node=C2=A0
=
or should it not be number of containers but sum of heap sizes?
<= div>
Cheers
Chris Mawata
--001a113ecad4252ce70509783cc6--