[
https://issues.apache.org/jira/browse/HADOOP-3130?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12588990#action_12588990
]
Amar Kamat commented on HADOOP-3130:
------------------------------------
bq. A minor point. Since UNIT_CONNECT_TIMEOUT is private final, the following
code segment seems redudant: ...
+1, removed.
bq. In case of exception that is not connection timeout, I think the right
behavior is to re-throw the exception.
I think there is no _good_ way of knowing whether its a connection-timeout
exception or not. So keeping it as it is.
> Shuffling takes too long to get the last map output.
> ----------------------------------------------------
>
> Key: HADOOP-3130
> URL: https://issues.apache.org/jira/browse/HADOOP-3130
> Project: Hadoop Core
> Issue Type: Bug
> Reporter: Runping Qi
> Assignee: Amar Kamat
> Attachments: HADOOP-3130-v2.patch, HADOOP-3130-v2.patch,
> HADOOP-3130-v3.1.patch, HADOOP-3130-v3.2.patch, HADOOP-3130-v3.patch,
> HADOOP-3130.patch, shuffling.log
>
>
> I noticed that towards the end of shufflling, the map output fetcher of the
> reducer backs off too aggressively.
> I attach a fraction of one reduce log of my job.
> Noticed that the last map output was not fetched in 2 minutes.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
