Return-Path: X-Original-To: apmail-hadoop-hdfs-user-archive@minotaur.apache.org Delivered-To: apmail-hadoop-hdfs-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 738FF1173C for ; Wed, 13 Aug 2014 08:44:35 +0000 (UTC) Received: (qmail 27425 invoked by uid 500); 13 Aug 2014 08:44:31 -0000 Delivered-To: apmail-hadoop-hdfs-user-archive@hadoop.apache.org Received: (qmail 27287 invoked by uid 500); 13 Aug 2014 08:44:31 -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 27277 invoked by uid 99); 13 Aug 2014 08:44:30 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 13 Aug 2014 08:44:30 +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 write2kishore@gmail.com designates 209.85.213.170 as permitted sender) Received: from [209.85.213.170] (HELO mail-ig0-f170.google.com) (209.85.213.170) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 13 Aug 2014 08:44:03 +0000 Received: by mail-ig0-f170.google.com with SMTP id h3so10519853igd.5 for ; Wed, 13 Aug 2014 01:44:02 -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=5ZajZuIe7T2vzeXwL8bmPv4EklUbLGyUdImNfwsHsEM=; b=dUli+8e42GCMBScvyznbSaA+vhMbyhkmGtVt1n93CDwSMWgDIKCiZ/koSYCMYLGa90 gxPXm86i3/NH5xFFzK8JdKnPi+nCXTY9NR0PBKKBlnJYueKmUTklUuiigy9meEdkcmbO ziIQOaXMBFmoa1nLU/QUjprD7cAc06RKliUOtPSywT9s45LVwzWmbd/BaaQkG74KAbVH nwLqY4UKwCmzydARrSzdox/VUzIsyonkZchDDR7dh15qItErvERgSwA41U/IHsjv/J3p YNpTKJVDhKFLVl46LGiuupbjm8bKA9WU29GFdwOFnplRqOfkh6Dja5ckE9jVOUVTXNWr Apuw== MIME-Version: 1.0 X-Received: by 10.50.50.198 with SMTP id e6mr46309861igo.1.1407919442733; Wed, 13 Aug 2014 01:44:02 -0700 (PDT) Received: by 10.43.162.69 with HTTP; Wed, 13 Aug 2014 01:44:02 -0700 (PDT) In-Reply-To: References: Date: Wed, 13 Aug 2014 14:14:02 +0530 Message-ID: Subject: Re: Negative value given by getVirtualCores() or getAvailableResources() From: Krishna Kishore Bonagiri To: user@hadoop.apache.org Content-Type: multipart/alternative; boundary=047d7bd75df241b43c05007eca7a X-Virus-Checked: Checked by ClamAV on apache.org --047d7bd75df241b43c05007eca7a Content-Type: text/plain; charset=UTF-8 Hi Wangda, I was actually wondering why should it give me -ve value for vcores when I call getAvailableResources(). Thanks, Kishore On Tue, Aug 12, 2014 at 12:50 PM, Wangda Tan wrote: > By default, vcore = 1 for each resource request. If you don't like this > behavior, you can set yarn.scheduler.minimum-allocation-vcores=0 > > Hope this helps, > Wangda Tan > > > > On Thu, Aug 7, 2014 at 7:13 PM, Krishna Kishore Bonagiri < > write2kishore@gmail.com> wrote: > >> Hi, >> I am calling getAvailableResources() on AMRMClientAsync and getting -ve >> value for the number virtual cores as below. Is there something wrong? >> >> . >> >> I have set the vcores in my yarn-site.xml like this, and just ran an >> application that requires two containers other than the Application >> Master's container. In the ContainerRequest setup from my >> ApplicationMaster, I haven't set anything for virtual cores, means I didn't >> call setVirtualCores() at all. >> >> So, I think it shouldn't be showing a -ve value for the vcores, when I >> call getAvailableResources(), am I wrong? >> >> >> Number of CPU cores that can be allocated for containers. >> >> yarn.nodemanager.resource.cpu-vcores >> 4 >> >> >> Thanks, >> Kishore >> > > --047d7bd75df241b43c05007eca7a Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Hi Wangda,

=C2=A0 I was actually wondering wh= y should it give me -ve value for vcores when I call getAvailableResources(= ).

Thanks,
Kishore


On Tue, Aug 12, 2014 at 12:50 PM, Wangda= Tan <wheeleast@gmail.com> wrote:
By default, vcore =3D 1 for each resource request. If you = don't like this behavior, you can set yarn.scheduler.minimum-allocation= -vcores=3D0=C2=A0

Hope this helps,
Wangda Tan<= /div>



On Thu, Au= g 7, 2014 at 7:13 PM, Krishna Kishore Bonagiri <write2kishore@gmail.= com> wrote:
Hi,
=C2=A0 I= am calling=C2=A0getAvailableResources() on=C2=A0AMRMClientAsync and gettin= g -ve value for the number virtual cores as below. Is there something wrong= ?

<memory:16110, vCores:-2&g= t;.

I have set the vcores in my yarn-site.xml like this, an= d just ran an application that requires two containers other than the Appli= cation Master's container. In the=C2=A0ContainerRequest setup from my A= pplicationMaster, I haven't set anything for virtual cores, means I did= n't call setVirtualCores() at all.

So, I think it shouldn't be showing a -ve value for= the vcores, when I call getAvailableResources(), am I wrong?

<description> Number of CPU cores tha= t can be allocated for containers. </description>
<name> yarn.nodemanager.resource.cpu-vcores </name>
<= div><value> 4 </value>
</property>
<= div>
Thanks,
Kishore


--047d7bd75df241b43c05007eca7a--