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 C3C2F182D2 for ; Sun, 23 Aug 2015 17:20:54 +0000 (UTC) Received: (qmail 94622 invoked by uid 500); 23 Aug 2015 17:20:48 -0000 Delivered-To: apmail-hadoop-common-user-archive@hadoop.apache.org Received: (qmail 94519 invoked by uid 500); 23 Aug 2015 17:20:48 -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 94509 invoked by uid 99); 23 Aug 2015 17:20:48 -0000 Received: from Unknown (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 23 Aug 2015 17:20:48 +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 BFD391827C2 for ; Sun, 23 Aug 2015 17:20:47 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 2.879 X-Spam-Level: ** X-Spam-Status: No, score=2.879 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=disabled Authentication-Results: spamd3-us-west.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from mx1-us-east.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id m38gS2c2IN6G for ; Sun, 23 Aug 2015 17:20:46 +0000 (UTC) Received: from mail-oi0-f45.google.com (mail-oi0-f45.google.com [209.85.218.45]) by mx1-us-east.apache.org (ASF Mail Server at mx1-us-east.apache.org) with ESMTPS id 3D2BE42921 for ; Sun, 23 Aug 2015 17:20:46 +0000 (UTC) Received: by oiey141 with SMTP id y141so67623116oie.1 for ; Sun, 23 Aug 2015 10:20:45 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=PN+bx7NVWbroWo/KDqF+oA3WJnm6ULs5tkqrKO1q/lk=; b=f3LPrwdbZ4yZOtLxW9Vrev9hfJ19o4aYT3SQR9I01NItQLXJB9xo/uRUJf0vdrbZUb rgtwfcm6KO8pQjswaRdy8xdf2sewrCGGbzmKCQe7d9/A8MgvAqGLt3lmI4MqRkYhb4yG XHIV6/q9TvBt73wOTya7VCCd5gZc0jIyyC105bzUJWbIMgoU4lYtOEGLu6V1xVzEqnaY jH1psHs6eXRmz3x5gMa7lLNMnRQUhTOv+PMt+vkLaakz3FI5D7//fXR6cTCIKQ/90mo9 msfmVRhoCWhaULWm7CbiVqo7YUpLxi9ZO+4im7BFgfR7Ua0Ni/AE1Z7Pr1jFxL3nW+pN uFug== MIME-Version: 1.0 X-Received: by 10.202.44.195 with SMTP id s186mr16595369ois.53.1440350445821; Sun, 23 Aug 2015 10:20:45 -0700 (PDT) Received: by 10.76.28.36 with HTTP; Sun, 23 Aug 2015 10:20:45 -0700 (PDT) In-Reply-To: References: Date: Sun, 23 Aug 2015 22:50:45 +0530 Message-ID: Subject: Re: yarn.nodemanager.resource.cpu-vcores vs yarn.scheduler.maximum-allocation-vcores From: Varun Saxena To: user@hadoop.apache.org Content-Type: multipart/alternative; boundary=001a11379ab8ace559051dfdb81f --001a11379ab8ace559051dfdb81f Content-Type: text/plain; charset=UTF-8 Hi Pedro, Real default value of yarn.scheduler.maximum-allocation-vcores is 4. The value of 32 is actually a documentation issue and has been fixed recently. Regards, Varun Saxena. On Sun, Aug 23, 2015 at 10:39 PM, Pedro Magalhaes wrote: > Varun, > Thanks for the reply. I undestand the arn.scheduler.maximum- > allocation-vcores parameter. I just asking why the default parameter is > yarn.scheduler.maximum-allocation-vcores=32. And > yarn.nodemanager.resource.cpu-vcores=8. > > In my opinion, if the yarn.scheduler.maximun-allocation-vcore is 32 tby > default the yarn.nodemanager.resource.cpu-vcores would be equal or greater > than 32, by default. > Is this make sense? > > > > > On Sun, Aug 23, 2015 at 2:00 PM, Varun Saxena > wrote: > >> Hi Pedro, >> >> Actual allocation would depend on the total resource capability >> advertised by NM while registering with RM. >> >> yarn.scheduler.maximum-allocation-vcores merely puts an upper cap on number of vcores which can be allocated by RM i.e. any Resource request/ask from AM which asks for vcores > 32(default value) for a container, will be normalized back to 32. >> >> If there is no such node available, this allocation will not be fulfilled. >> >> yarn.scheduler.maximum-allocation-vcores will be configured in resource >> manager and hence will be common for a cluster which can possibly have >> multiple nodes with heterogeneous resource capabilities >> >> yarn.nodemanager.resource.cpu-vcores on the other hand will have to be >> configured as per resource capability of that particular node. >> >> Recently there has been work done to automatically get memory and CPU >> information from underlying OS(supported OS being Linux and Windows) if >> configured to do so. This change would be available in 2.8 >> I hope this answers your question. >> >> Regards, >> Varun Saxena. >> >> On Sun, Aug 23, 2015 at 9:40 PM, Pedro Magalhaes >> wrote: >> >>> I was looking at default parameters for: >>> >>> yarn.nodemanager.resource.cpu-vcores = 8 >>> yarn.scheduler.maximum-allocation-vcores = 32 >>> >>> For me this two parameters as default doesnt make any sense. >>> >>> The first one say "the number of CPU cores that can be allocated for >>> containers." (I imagine that is vcore) The seconds says: "The maximum >>> allocation for every container request at the RM". In my opinion, the >>> second one must be equal or less than the first one. >>> >>> How can allocate 32 vcores for a container if i have only 8 cores >>> available per container? >>> >> >> > --001a11379ab8ace559051dfdb81f Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Hi Pedro,

Real default value of yarn.= scheduler.maximum-allocation-vcores is 4.
T= he value of 32 is actually a documentation issue and has been fixed recentl= y.

Reg= ards,
Varun Saxena.


On Sun, Aug 23, 2015 at 10:39 PM, Pedro Magalhaes <<= a href=3D"mailto:pedrorjbr@gmail.com" target=3D"_blank">pedrorjbr@gmail.com= > wrote:
V= arun,
Thanks for the reply. I undestand the=C2=A0arn.scheduler.maximum-allocation-vcores=C2=A0parameter. I = just asking why the default parameter is yarn.scheduler.maximum-allocation-vcores=3D32.=C2=A0And=C2=A0yarn.nodemanager.resource.cpu-vcores=3D8.

In my opinion, if the yarn.scheduler.maximun-allocati= on-vcore is 32 tby default the yarn.nodemanager.resource.cpu-vcores =C2=A0w= ould be equal or greater than 32, by default.
Is this make sense?=




On Sun, Aug 23, 2015 at 2:00 PM, Varun Saxena <vsaxena.varun@gm= ail.com> wrote:
Hi Pedro,

Actual allocation would depend on the to= tal resource capability advertised by NM while registering with RM.
=
yarn.scheduler.maximum-allocation-vcores=
 merely puts an upper cap on number of vcores which can be allocated by RM =
i.e. any Resource request/ask from AM which asks for vcores > 32(default=
 value) for a container, will be normalized back to 32.
If there is no such node available, this allocatio=
n will not be fulfilled.
yarn.scheduler.maximum-allo= cation-vcores will be configured in resource manager and hence will be comm= on for a cluster which can possibly have multiple nodes with heterogeneous = resource capabilities

yarn.nodemanager.resource.cp= u-vcores on the other hand will have to be configured as per resource capab= ility of that particular node.=C2=A0

Recently ther= e has been work done to automatically get memory and CPU information from u= nderlying OS(supported OS being Linux and Windows) if configured to do so. = This change would be available in 2.8
I hope this answers your qu= estion.

Regards,
Varun Saxena.

On Su= n, Aug 23, 2015 at 9:40 PM, Pedro Magalhaes <pedrorjbr@gmail.com&g= t; wrote:

I was looking at default parameters for:

yarn.nodemana=
ger.resource.cpu-vcores =3D 8
yarn.scheduler.maximum-allocation-vcores =3D 32

For me this two parameters as default doesnt mak= e any sense.

The first one say "the number of CPU cor= es that can be allocated for containers." (I imagine that is vcore) Th= e seconds says: "The maximum allocation for every container request at= the RM". In my opinion, the second one must be equal or less than the= first one.

How can allocate 32 vcores for a container if = i have only 8 cores available per container?




--001a11379ab8ace559051dfdb81f--