Return-Path: X-Original-To: apmail-hadoop-user-archive@minotaur.apache.org Delivered-To: apmail-hadoop-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 236B5C752 for ; Fri, 7 Jun 2013 15:55:54 +0000 (UTC) Received: (qmail 94883 invoked by uid 500); 7 Jun 2013 15:55:49 -0000 Delivered-To: apmail-hadoop-user-archive@hadoop.apache.org Received: (qmail 94367 invoked by uid 500); 7 Jun 2013 15:55:44 -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 94359 invoked by uid 99); 7 Jun 2013 15:55:44 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 07 Jun 2013 15:55:44 +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 rahul.rec.dgp@gmail.com designates 209.85.212.54 as permitted sender) Received: from [209.85.212.54] (HELO mail-vb0-f54.google.com) (209.85.212.54) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 07 Jun 2013 15:55:38 +0000 Received: by mail-vb0-f54.google.com with SMTP id f13so2841999vbg.13 for ; Fri, 07 Jun 2013 08:55:17 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:from:date:message-id:subject:to:content-type; bh=aM7u4BzF4ZnaE3W1gfMC3Mp4ZEZP6gkzh1AyxyWvgT0=; b=NEFCNaKmS7wwnhI0xWAP22CzEatm4khe+bgZrG1yQNM+JlZLyaqt9reoI2G8sELJpm PYpNiAEqkZjTBeQOdxeZdn50yxDnpQ0jmG73lc1nids4XyaFc/EKCU3Q0AjyZqkoCeB8 0hFNMFrx2hJn9dpl245mDbMFCaNbIHoL5G5z3CZbIf0MyQwS7PTVvSaPsrAdCIMYrNGJ OD7VLRMmOn88byaYW6usbFUqZpl+d67KxRqvQ2yPTR0leIQU9Y51PTH2aABv0rvQgp4s b4CdfcW6g+Brpm7hX/AE9wo1+fSlu0mR+scloA0Y1GA+FR82Ao/Z8O492jgUaesD0szB HmwQ== X-Received: by 10.52.243.234 with SMTP id xb10mr20399433vdc.68.1370620517534; Fri, 07 Jun 2013 08:55:17 -0700 (PDT) MIME-Version: 1.0 Received: by 10.59.6.68 with HTTP; Fri, 7 Jun 2013 08:54:57 -0700 (PDT) From: Rahul Bhattacharjee Date: Fri, 7 Jun 2013 21:24:57 +0530 Message-ID: Subject: Resource manager question - Yarn To: "user@hadoop.apache.org" Content-Type: multipart/alternative; boundary=001a11c1c7dc1352d404de9275cb X-Virus-Checked: Checked by ClamAV on apache.org --001a11c1c7dc1352d404de9275cb Content-Type: text/plain; charset=UTF-8 Hello, I have a basic question related to RM of Yarn. Why is the allocate container request to RM doesn't always return with containers. The call can actually block and return when containers are available. Scenario : I launcher AM. The AM requests for 5 containers. The response returns without any containers. I send the request for containers , again and again and the RM returns containers (sometimes less than the number that I have asked for). Is this something to do with the heartbeat as the allocate call must return within a predictable time period? Thanks, Rahul --001a11c1c7dc1352d404de9275cb Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Hello,

I have a basic question related to RM of Yarn. Why is the allocate container= request to RM=20 doesn't always return with containers. The call can actually block and = return when containers are available.

= Scenario :

I launcher AM.
The AM requests for 5 containers.
=
The response returns without any containers.

I send the request for containers , again and again and the RM returns=20 containers (sometimes less than the number that I have asked for).

= Is this something to do with the heartbeat as the allocate call must return= within a predictable time period?

Thanks,
Rahul
--001a11c1c7dc1352d404de9275cb--