hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Doug Cutting (JIRA)" <j...@apache.org>
Subject [jira] Closed: (HADOOP-218) Inefficient calls to get configuration values in TaskInprogress
Date Mon, 05 Jun 2006 23:08:55 GMT
     [ http://issues.apache.org/jira/browse/HADOOP-218?page=all ]
     
Doug Cutting closed HADOOP-218:
-------------------------------


> Inefficient calls to get configuration values in TaskInprogress
> ---------------------------------------------------------------
>
>          Key: HADOOP-218
>          URL: http://issues.apache.org/jira/browse/HADOOP-218
>      Project: Hadoop
>         Type: Improvement

>   Components: mapred
>     Reporter: Mahadev konar
>     Assignee: Mahadev konar
>     Priority: Minor
>      Fix For: 0.3.0
>  Attachments: speculative.patch
>
> Each time a pollforNewTask in called on the JobTracker, the taskinprogress makes a call
to hasSpeculativeTask() which current does a conf.getSpeculativeExecution() each time its
called. The fix would be to store it in the TaskInProgress as soon as it is created and make
only a single call to conf.getSpeculativeExecution().

-- 
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


Mime
View raw message