All nodes are in sync configuration wise. We have a few cluster scripts that
ensure this is the case.
On 13 May 2011 06:55, Harsh J ha...@cloudera.com wrote:
One of the reasons I can think of could be a version mismatch. You may
want to ensure that the job in question was not carrying a
Hi there,
I'm experiencing some unusual behaviour on our 0.20.2 hadoop cluster.
Randomly (periodically), we're getting Call to namenode failures on
tasktrackers causing tasks to fail:
2011-05-12 14:36:37,462 WARN org.apache.hadoop.mapred.TaskRunner:
attempt_201105090819_059_m_0038_0Child Error
One of the reasons I can think of could be a version mismatch. You may
want to ensure that the job in question was not carrying a separate
version of Hadoop along with it inside, perhaps?
On Fri, May 13, 2011 at 12:42 AM, Sidney Simmons
ssimm...@nmitconsulting.co.uk wrote:
Hi there,
I'm
