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 867C019C1F for ; Sat, 2 Apr 2016 12:36:42 +0000 (UTC) Received: (qmail 22650 invoked by uid 500); 2 Apr 2016 12:36:37 -0000 Delivered-To: apmail-hadoop-common-user-archive@hadoop.apache.org Received: (qmail 22531 invoked by uid 500); 2 Apr 2016 12:36:37 -0000 Mailing-List: contact user-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list user@hadoop.apache.org Received: (qmail 22519 invoked by uid 99); 2 Apr 2016 12:36:37 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 02 Apr 2016 12:36:37 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id 1A4DFC21D8 for ; Sat, 2 Apr 2016 12:36:37 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 1.198 X-Spam-Level: * X-Spam-Status: No, score=1.198 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=2, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001] autolearn=disabled Authentication-Results: spamd1-us-west.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id YkLsqkJXIdFt for ; Sat, 2 Apr 2016 12:36:36 +0000 (UTC) Received: from mail-lb0-f172.google.com (mail-lb0-f172.google.com [209.85.217.172]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTPS id 9BCB55F572 for ; Sat, 2 Apr 2016 12:36:35 +0000 (UTC) Received: by mail-lb0-f172.google.com with SMTP id qe11so96889915lbc.3 for ; Sat, 02 Apr 2016 05:36:35 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=to:from:subject:message-id:date:user-agent:mime-version; bh=H5n6kssPERJE67z+UljS5eDYlDYzEtZB5Yqr9Tj2Y6I=; b=v8FYptyMyOwz+oxyZvwoEPuOOYbsreDnjqA7oRgSg9HwI+r5aakwpujhw4c0uQjcsJ KWj5TkFDbMZctlLgnPC7ZqJFb4pbyZiW1aV569NZ+QdDi2MtQy9o4cdrvA/UdkvWbZ43 SW6vUzRpGvxWzSDwLSTMOkegutJnK21cmi9c8JI1ErQ+znBuXPX+xfAJGxZJTGpxLtb6 LAQG/J2CZ1FnD0LWImsnJdzk0xwAzPWecB5jjjfW1QVAaa853Iwotuvc+Q+cL2XxzrNe 8La1P5nA/ZVsPgSMfc/hwUa65gqOJDz6uXiGYYiii9STWvHa1xLVd/+50TEvU+/wqVzR IbJw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:to:from:subject:message-id:date:user-agent :mime-version; bh=H5n6kssPERJE67z+UljS5eDYlDYzEtZB5Yqr9Tj2Y6I=; b=Kk6Ey/6idYmcdT8buXUbhIxBzpFfAmGCqbYZsQKcbTegAFhFWQRGn6qhQ/FfbLUUqm 6CGkrFeaNw7bgj7hlPs5kJEC4T/tn9/R4akKq/QdKu8rf9NaSJytzyto/sqAzACSEfas LoBcEjSIGrF9ZxhEeWp4QNTE7S2CcA0YvHyillLVXAQ+LbgmB84T6kPBxcqqPcmfP1gw tQiwhXP2dy/kNCwIUiWYzADd8bXFieXgt/TL7jzFBmmPNS+wHVQGmELEctfoSVicwVFK LN26gTYYfuvCvdh9mKBS8wNnTXKT7EJ0T2Ya5pgOaieETM3VY4klKHlCZJq3AQftp/Fs AHoQ== X-Gm-Message-State: AD7BkJLYEV6ixpXTWHSS1jHjYTR2kuTKFNcyN/dDvwJr2ZQZx9s4k7Zsg7HsWPUesLRTIA== X-Received: by 10.28.234.69 with SMTP id i66mr3212932wmh.96.1459600594117; Sat, 02 Apr 2016 05:36:34 -0700 (PDT) Received: from [192.168.10.108] (bl10-159-191.dsl.telepac.pt. [85.243.159.191]) by smtp.gmail.com with ESMTPSA id j18sm3725190wmd.2.2016.04.02.05.36.33 for (version=TLSv1/SSLv3 cipher=OTHER); Sat, 02 Apr 2016 05:36:33 -0700 (PDT) To: user@hadoop.apache.org From: xeonmailinglist Subject: Run Yarn with 2GB of RAM and 1 CPU core Message-ID: <56FFBCD0.1070804@gmail.com> Date: Sat, 2 Apr 2016 13:36:32 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.6.0 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="------------030807090800090804060100" --------------030807090800090804060100 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit I have configured Hadoop Yarn in a VM with 2048MB of RAM and 1 CPU core. Then, I have configured the max and the min limits of memory to be used in Yarn in the |mapred-site.xml| | yarn.scheduler.minimum-allocation-mb 1024 yarn.scheduler.maximum-allocation-mb 2048 yarn.scheduler.minimum-allocation-vcores 1 yarn.scheduler.maximum-allocation-vcores 1 yarn.nodemanager.resource.memory-mb 2048 yarn.nodemanager.resource.cpu-vcores 1 | But when I run an example, the count words on a file with 32K, the job simply won’t run. It always stays at |0%|. I have tried to decrease both values in the |mapred-site.xml| to |1024| and |512|, respectively, but the job couldn’t also run. Therefore, I have kept the |2048| and |1024| values. To try to understand what is going on, I have looked to the Yarn logs, but I haven’t find much useful information. I have just found was this line, but it seems that everything is ok. |2016-04-01 12:15:51,728 INFO org.apache.hadoop.yarn.server.nodemanager.containermanager.monitor.ContainersMonitorImpl: Starting resource-monitoring for container_1459527184896_0001_01_000001 2016-04-01 12:15:51,797 INFO org.apache.hadoop.yarn.server.nodemanager.containermanager.monitor.ContainersMonitorImpl: Memory usage of ProcessTree 29808 for container-id container_1459527184896_0001_01_000001: 48.9 MB of 2 GB physical memory used; 1.1 GB of 4.2 GB virtual memory used | I don’t know why my example won’t work. Any help to debug this problem? Is it possible to run a job in a VM with 2048GB of RAM and 1 CPU core? ​ --------------030807090800090804060100 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 8bit

I have configured Hadoop Yarn in a VM with 2048MB of RAM and 1 CPU core. Then, I have configured the max and the min limits of memory to be used in Yarn in the mapred-site.xml

 <property> <name>yarn.scheduler.minimum-allocation-mb</name> <value>1024</value> </property>
 <property> <name>yarn.scheduler.maximum-allocation-mb</name> <value>2048</value> </property>
 <property> <name>yarn.scheduler.minimum-allocation-vcores</name> <value>1</value> </property>
 <property> <name>yarn.scheduler.maximum-allocation-vcores</name> <value>1</value> </property>
 <property> <name>yarn.nodemanager.resource.memory-mb</name> <value>2048</value> </property>
 <property> <name>yarn.nodemanager.resource.cpu-vcores</name> <value>1</value> </property>

But when I run an example, the count words on a file with 32K, the job simply won’t run. It always stays at 0%.

I have tried to decrease both values in the mapred-site.xml to 1024 and 512, respectively, but the job couldn’t also run. Therefore, I have kept the 2048 and 1024 values.

To try to understand what is going on, I have looked to the Yarn logs, but I haven’t find much useful information. I have just found was this line, but it seems that everything is ok.

2016-04-01 12:15:51,728 INFO org.apache.hadoop.yarn.server.nodemanager.containermanager.monitor.ContainersMonitorImpl: Starting resource-monitoring for container_1459527184896_0001_01_000001
2016-04-01 12:15:51,797 INFO org.apache.hadoop.yarn.server.nodemanager.containermanager.monitor.ContainersMonitorImpl: Memory usage of ProcessTree 29808 for container-id container_1459527184896_0001_01_000001: 48.9 MB of 2 GB physical memory used; 1.1 GB of 4.2 GB virtual memory used

I don’t know why my example won’t work. Any help to debug this problem? Is it possible to run a job in a VM with 2048GB of RAM and 1 CPU core?

​
--------------030807090800090804060100--