[
https://issues.apache.org/jira/browse/HADOOP-3130?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12585567#action_12585567
]
Amar Kamat commented on HADOOP-3130:
------------------------------------
bq. Did you also change the timeout for read?
No.
bq. what is the value for Exceeded MAX_FAILED_UNIQUE_FETCHES?
5 (as in trunk)
bq. Should that be some percentage of the total num of maps?
I think 3min read timeout and exponential backoff work well. But yes it needs
to be reworked (moving some logic to JT etc).
> 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.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.
