Hadoop-Common-trunk - Build # 743 - Still Failing

2011-07-11 Thread Apache Jenkins Server
See https://builds.apache.org/job/Hadoop-Common-trunk/743/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 25265 lines...] [tar] Nothing to do: /grid/0/huds

Re: "java.lang.Throwable: Child Error " And " Task process exit with nonzero status of 1."

2011-07-11 Thread Bharath Mundlapudi
That number is around 40K (I think). I am not sure if you have certain configurations to cleanup user task logs periodically. We have solved this problem in MAPREDUCE-2415 which part of 0.20.204. But you cleanup the task logs periodically, you will not run into this problem. -Bharath

[jira] [Created] (HADOOP-7457) Remove out-of-date Chinese language documentation

2011-07-11 Thread Jakob Homan (JIRA)
Remove out-of-date Chinese language documentation - Key: HADOOP-7457 URL: https://issues.apache.org/jira/browse/HADOOP-7457 Project: Hadoop Common Issue Type: Improvement Components:

Re: "java.lang.Throwable: Child Error " And " Task process exit with nonzero status of 1."

2011-07-11 Thread C.V.Krishnakumar Iyer
Hi, I get this error too. But the Job completes properly. Is this error any cause for concern? As in, would any computation be hampered because of this? Thanks ! Regards, Krishnakumar On Jul 11, 2011, at 10:53 AM, Bharath Mundlapudi wrote: > That number is around 40K (I think). I am not sure i

[jira] [Resolved] (HADOOP-7456) Connection with RemoteException is not removed from cached HashTable and cause memory leak

2011-07-11 Thread Angelo K. Huang (JIRA)
[ https://issues.apache.org/jira/browse/HADOOP-7456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Angelo K. Huang resolved HADOOP-7456. - Resolution: Duplicate > Connection with RemoteException is not removed from cached HashT

Re: "java.lang.Throwable: Child Error " And " Task process exit with nonzero status of 1."

2011-07-11 Thread Harsh J
The job may have succeeded due to the task having run successfully on another tasktracker after a retry attempt was scheduled. This probably means one of your TT has something bad on it, and should be easily identifiable from the UI. If all TTs are bad, your job would fail -- so yes, better to fix