Mailing-List: contact mapreduce-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: mapreduce-issues@hadoop.apache.org
Date: Mon, 21 Jul 2014 17:54:41 +0000 (UTC)
From: "Allen Wittenauer (JIRA)" <jira@apache.org>
To: mapreduce-issues@hadoop.apache.org
Message-ID: <JIRA.12411591.1230917492741.10809.1405965281969@arcas>
In-Reply-To: <JIRA.12411591.1230917492741@arcas>
References: <JIRA.12411591.1230917492741@arcas>
Subject: [jira] [Resolved] (MAPREDUCE-154) Mapper runs out of memory
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/MAPREDUCE-154?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Allen Wittenauer resolved MAPREDUCE-154.
----------------------------------------

    Resolution: Cannot Reproduce

> Mapper runs out of memory
> -------------------------
>
>                 Key: MAPREDUCE-154
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-154
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>         Environment: Amazon EC2 Extra Large instance (4 cores, 15 GB RAM), Sun Java 6 (1.6.0_10); 1 Master, 4 Slaves (all the same); each Java process takes the argument "-Xmx700m" (2 Java processes per Instance)
>            Reporter: Richard J. Zak
>
> The hadoop job has the task of processing 4 directories in HDFS, each with 15 files.  This is sample data, a test run, before I go to the needed 5 directories of about 800 documents each.  The mapper takes in nearly 200 pages (not files) and throws an OutOfMemory exception.  The largest file is 17 MB.
> If this problem is something on my end and not truly a bug, I apologize.  However, after Googling a bit, I did see many threads of people running out of memory with small data sets.


--
This message was sent by Atlassian JIRA
(v6.2#6252)