Re: Task process exit with nonzero status of 134

2009-07-28 Thread Todd Lipcon
Youch! Thanks for the followup. Confirmed that that Crasher.java snippet crashes my Sun 1.6.0 update 14 as well. Hopefully they'll get it fixed in update 15 -Todd On Tue, Jul 28, 2009 at 7:00 AM, Christian Kirschbaum < christian.kirschb...@vionto.com> wrote: > Hi Todd et al., > > coming back to

Re: Task process exit with nonzero status of 134

2009-07-28 Thread Christian Kirschbaum
Hi Todd et al., coming back to this again, I'd like to present a solution we found and that indeed a JVM bug was the cause of seeing exit code 134 on the TaskRunner. First of all, we had to configure the Hadoop subsystem to start with the following parameter: -XX:ErrorFile=/opt/hadoop/hado

Re: What does MAX_FAILED_UNIQUE_FETCHES mean?

2009-07-28 Thread Jason Venner
I have seen this happen when there are inconsistent hostname to ip address lookups across the cluster and a node running a reducer is not connecting to the host that actually has the map output due to getting a different ip address for the node name. On Mon, Jul 27, 2009 at 9:46 AM, Geoffry Robert