I met the same problem on window+cygwin, don't know the root cause, but it
can be worked around by a explicit mapred.child.tmp property. Try add
these lines to your conf/mapred-site.xml:
property
namemapred.child.tmp/name
value/tmp/hadoop/mapred/mapred.child.tmp/value
/property
already tried that. Are you using 0.20.2?
Thank you,
Carlos Eduardo
On Sun, May 9, 2010 at 8:34 AM, Yang Li liy...@cn.ibm.com wrote:
I met the same problem on window+cygwin, don't know the root cause, but
it
can be worked around by a explicit mapred.child.tmp property. Try add
these lines to your
I met the same problem on WinXP+Cygwin and fixed it by
either:
- moving to a linux box (VMWare works very well)
or:
- configuring a mapred.child.tmp parameter in core-site.xml
I cannot explain why and how mapred.child.tmp is related to the problem.
From source code, it seems to be a JVM issue on
