[
https://issues.apache.org/jira/browse/HADOOP-3327?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12593444#action_12593444
]
rangadi edited comment on HADOOP-3327 at 4/30/08 2:35 PM:
---------------------------------------------------------------
>2008-04-30 17:25:45,005 WARN org.apache.hadoop.mapred.TaskTracker:
>getMapOutput(task_200804301615_0003_m_000756_0,653) failed :
java.net.SocketException: Connection timed out
> -
> at org.mortbay.http.HttpOutputStream.write(HttpOutputStream.java:423)
> at org.mortbay.jetty.servlet.ServletOut.write(ServletOut.java:54)
"Connection timed out" error while writing indicates the root cause is mostly
the same packet retransmission problem seen in HADOOP-3132.
was (Author: rangadi):
>2008-04-30 17:25:45,005 WARN org.apache.hadoop.mapred.TaskTracker:
getMapOutput(task_200804301615_0003_m_000756_0,653) failed :
java.net.SocketException: Connection timed out
> -
> at org.mortbay.http.HttpOutputStream.write(HttpOutputStream.java:423)
> at org.mortbay.jetty.servlet.ServletOut.write(ServletOut.java:54)
"Connection timed out" error while writing indicates the root cause is most the
same packet retransmission problem seen in HADOOP-3132.
> Shufflinge fetachers waited too long between map output fetch re-tries
> ----------------------------------------------------------------------
>
> Key: HADOOP-3327
> URL: https://issues.apache.org/jira/browse/HADOOP-3327
> Project: Hadoop Core
> Issue Type: Bug
> Components: mapred
> Reporter: Runping Qi
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
