Peter Chu 2013-05-26, 19:04
Looks are you getting the error in hive shell? You can control client
memory usage by setting HADOOP_HEAPSIZE in conf/hadoop-env.sh.
On Mon, May 27, 2013 at 12:34 AM, Peter Chu <[EMAIL PROTECTED]> wrote:
> Hi, I ran into memory problem while using Map Join. Errors below, how do
> I increase the map join memory size and if there are other solutions?
> Execution log at: /tmp/hadoop/hadoop_20130525231414_3cc50fdd-7e7a-4bcf-baab-b465804c6e49.log
> 2013-05-25 11:14:41 Starting to launch local task to process map join; maximum memory = 932118528
> SLF4J: Class path contains multiple SLF4J bindings.
> SLF4J: Found binding in [jar:file:/home/hadoop/lib/slf4j-log4j12-1.6.1.jar!/org/slf4j/impl/StaticLoggerBinder.class]
> SLF4J: Found binding in [jar:file:/home/hadoop/.versions/hive-0.8.1/lib/slf4j-log4j12-1.6.1.jar!/org/slf4j/impl/StaticLoggerBinder.class]
> SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an explanation.
> 2013-05-25 11:15:04 Processing rows: 200000 Hashtable size: 199999 Memory usage: 776903128 rate: 0.833
> 2013-05-25 11:15:09 Processing rows: 214614 Hashtable size: 214614 Memory usage: 811592328 rate: 0.871
> 2013-05-25 11:15:09 Dump the hashtable into file: file:/tmp/hadoop/hive_2013-05-25_23-14-39_270_9001068894438685980/-local-10006/HashTable-Stage-6/MapJoin-bu-21--.hashtable
> Execution failed with exit status: 2
> Obtaining error information
> Task failed!
> Task ID:
The information contained in this communication is intended solely for the
use of the individual or entity to whom it is addressed and others
authorized to receive it. It may contain confidential or legally privileged
information. If you are not the intended recipient you are hereby notified
that any disclosure, copying, distribution or taking any action in reliance
on the contents of this information is strictly prohibited and may be
unlawful. If you have received this communication in error, please notify
us immediately by responding to this email and then delete it from your
system. The firm is neither liable for the proper and complete transmission
of the information contained in this communication nor for any delay in its