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 "Mahadev konar (JIRA)" <ji...@apache.org> on 2006/05/15 00:09:05 UTC

[jira] Created: (HADOOP-218) Inefficient calls to get configuration values in TaskInprogress

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
 Assigned to: Mahadev konar 
    Priority: Minor


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

[jira] Resolved: (HADOOP-218) Inefficient calls to get configuration values in TaskInprogress

Posted by "Doug Cutting (JIRA)" <ji...@apache.org>.
     [ http://issues.apache.org/jira/browse/HADOOP-218?page=all ]
     
Doug Cutting resolved HADOOP-218:
---------------------------------

    Fix Version: 0.3
     Resolution: Fixed

I just committed this.  Thanks, Mahadev!

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

[jira] Closed: (HADOOP-218) Inefficient calls to get configuration values in TaskInprogress

Posted by "Doug Cutting (JIRA)" <ji...@apache.org>.
     [ 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

[jira] Updated: (HADOOP-218) Inefficient calls to get configuration values in TaskInprogress

Posted by "Mahadev konar (JIRA)" <ji...@apache.org>.
     [ http://issues.apache.org/jira/browse/HADOOP-218?page=all ]

Mahadev konar updated HADOOP-218:
---------------------------------

    Attachment: speculative.patch

Here is a patch, that gets the configuration value once and stores it in the TaskInProgress.

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