You are viewing a plain text version of this content. The canonical link for it is here.
Posted to mapreduce-issues@hadoop.apache.org by "Siddharth Seth (JIRA)" <ji...@apache.org> on 2012/05/01 23:36:53 UTC
[jira] [Commented] (MAPREDUCE-4217) Task commit waits for up to 3
seconds
[ https://issues.apache.org/jira/browse/MAPREDUCE-4217?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13266143#comment-13266143 ]
Siddharth Seth commented on MAPREDUCE-4217:
-------------------------------------------
Tom, this looks to be the same as MAPREDUCE-3809 - which went in a while ago. Are you still seing the 3 second wait ?
> Task commit waits for up to 3 seconds
> -------------------------------------
>
> Key: MAPREDUCE-4217
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-4217
> Project: Hadoop Map/Reduce
> Issue Type: Improvement
> Components: task
> Affects Versions: 0.23.1
> Reporter: Tom White
> Assignee: Tom White
>
> Following MAPREDUCE-2450, TaskReporter#stopCommunicationThread may wait up to 3 seconds (the value of PROGRESS_INTERVAL) before it returns. This can be noticeable for short running tasks.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira