Thanks guys, I'll get with operations to do the upgrade.
Chris
On Mon, Dec 5, 2011 at 4:11 PM, Bejoy Ks wrote:
> Hi Chris
> From the stack trace, it looks like a JVM corruption issue. It is
> a known issue and have been fixed in CDH3u2, i believe an upgrade would
> solve your issues.
>
Hi Chris
From the stack trace, it looks like a JVM corruption issue. It is
a known issue and have been fixed in CDH3u2, i believe an upgrade would
solve your issues.
https://issues.apache.org/jira/browse/MAPREDUCE-3184
Then regarding your queries,I'd try to help you out a bit.In mapreduce
Hi Chris,
I'd suggest updating to a newer version of your hadoop distro - you're
hitting some bugs that were fixed last summer. In particular, you're
missing the "amendment" patch from MAPREDUCE-2373 as well as some
patches to MR which make the fetch retry behavior more aggressive.
-Todd
On Mon,
Hi,
Using: *Version:* 0.20.2-cdh3u0, r81256ad0f2e4ab2bd34b04f53d25a6c23686dd14,
8 node cluster, 64 bit Centos
We are occasionally seeing MAX_FETCH_RETRIES_PER_MAP errors on reducer
jobs. When we investigate it looks like the TaskTracker on the node being
fetched from is not running. Looking at th
