You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-dev@hadoop.apache.org by "Owen O'Malley (JIRA)" <ji...@apache.org> on 2006/06/01 20:13:29 UTC
[jira] Created: (HADOOP-268) TaskTracker latency is slowing down
maps because progress reporting is done inline
TaskTracker latency is slowing down maps because progress reporting is done inline
----------------------------------------------------------------------------------
Key: HADOOP-268
URL: http://issues.apache.org/jira/browse/HADOOP-268
Project: Hadoop
Type: Improvement
Components: mapred
Versions: 0.2.1
Reporter: Owen O'Malley
Assigned to: Sameer Paranjpye
Fix For: 0.4
Moving the progress reporter to a separate thread should free up the user application to run faster.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Updated: (HADOOP-268) TaskTracker latency is slowing down
maps because progress reporting is done inline
Posted by "Doug Cutting (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/HADOOP-268?page=all ]
Doug Cutting updated HADOOP-268:
--------------------------------
Fix Version: 0.5.0
(was: 0.4.0)
> TaskTracker latency is slowing down maps because progress reporting is done inline
> ----------------------------------------------------------------------------------
>
> Key: HADOOP-268
> URL: http://issues.apache.org/jira/browse/HADOOP-268
> Project: Hadoop
> Type: Improvement
> Components: mapred
> Versions: 0.2.1
> Reporter: Owen O'Malley
> Assignee: Sameer Paranjpye
> Fix For: 0.5.0
>
> Moving the progress reporter to a separate thread should free up the user application to run faster.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Resolved: (HADOOP-268) TaskTracker latency is slowing down
maps because progress reporting is done inline
Posted by "Owen O'Malley (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-268?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Owen O'Malley resolved HADOOP-268.
----------------------------------
Resolution: Duplicate
Fix Version/s: 0.14.0
Assignee: (was: Sanjay Dahiya)
This was fixed by HADOOP-1462.
> TaskTracker latency is slowing down maps because progress reporting is done inline
> ----------------------------------------------------------------------------------
>
> Key: HADOOP-268
> URL: https://issues.apache.org/jira/browse/HADOOP-268
> Project: Hadoop
> Issue Type: Improvement
> Components: mapred
> Affects Versions: 0.2.1
> Reporter: Owen O'Malley
> Fix For: 0.14.0
>
>
> Moving the progress reporter to a separate thread should free up the user application to run faster.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (HADOOP-268) TaskTracker latency is slowing down
maps because progress reporting is done inline
Posted by "Sameer Paranjpye (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/HADOOP-268?page=all ]
Sameer Paranjpye reassigned HADOOP-268:
---------------------------------------
Assignee: Sanjay Dahiya (was: Sameer Paranjpye)
> TaskTracker latency is slowing down maps because progress reporting is done inline
> ----------------------------------------------------------------------------------
>
> Key: HADOOP-268
> URL: http://issues.apache.org/jira/browse/HADOOP-268
> Project: Hadoop
> Issue Type: Improvement
> Components: mapred
> Affects Versions: 0.2.1
> Reporter: Owen O'Malley
> Assigned To: Sanjay Dahiya
> Fix For: 0.6.0
>
>
> Moving the progress reporter to a separate thread should free up the user application to run faster.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira