Re: No Space left on device

2012-04-26 Thread Sidney Simmons
Might be worth checking your inode usage as lack of inodes will result in the same error HTH On 26 Apr 2012, at 07:01, Harsh J ha...@cloudera.com wrote: The transient Map-Reduce files do not go to the DFS, but rather onto the local filesystem directories specified by the mapred.local.dir

Re: Call to namenode fails with java.io.EOFException

2011-05-13 Thread Sidney Simmons
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 experiencing some unusual behaviour on our 0.20.2 hadoop cluster. Randomly (periodically), we're getting Call to namenode failures

Re: Call to namenode fails (java.io.EOFException)

2011-05-13 Thread Sidney Simmons
iPhone On May 12, 2011, at 3:56 PM, Sidney Simmons ssimm...@nmitconsulting.co.uk wrote: Hi there, Apologies if this comes through twice but i sent the mail a few hours ago and haven't seen it on the mailing list. I'm experiencing some unusual behaviour on our 0.20.2 hadoop cluster

Call to namenode failures

2011-05-12 Thread Sidney Simmons
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

Call to namenode fails with java.io.EOFException

2011-05-12 Thread Sidney Simmons
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

Call to namenode fails (java.io.EOFException)

2011-05-12 Thread Sidney Simmons
Hi there, Apologies if this comes through twice but i sent the mail a few hours ago and haven't seen it on the mailing list. 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