hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Owen O'Malley (JIRA)" <j...@apache.org>
Subject [jira] Updated: (HADOOP-2790) TaskInProgress.hasSpeculativeTask is very inefficient
Date Sun, 02 Mar 2008 08:40:50 GMT

     [ https://issues.apache.org/jira/browse/HADOOP-2790?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Owen O'Malley updated HADOOP-2790:
----------------------------------

       Resolution: Fixed
    Fix Version/s:     (was: 0.16.1)
                   0.17.0
           Status: Resolved  (was: Patch Available)

Devaraj, the original patch would have worked for 0.16, but for now l decided to just put
it in trunk.

> TaskInProgress.hasSpeculativeTask is very inefficient
> -----------------------------------------------------
>
>                 Key: HADOOP-2790
>                 URL: https://issues.apache.org/jira/browse/HADOOP-2790
>             Project: Hadoop Core
>          Issue Type: Bug
>          Components: mapred
>            Reporter: Owen O'Malley
>            Assignee: Owen O'Malley
>             Fix For: 0.17.0
>
>         Attachments: 2790-2.patch, 2790.patch
>
>
> Each call to JobInProgress.findNewTask can call TaskInProgress.hasSpeculativeTask once
per a task. Each call to hasSpeculativeTask calls System.getCurrentTimeMillis, which can result
in hundreds of thousands of calls to getCurrentTimeMillis. Additionally, it calls TaskInProgress.isOnlyCommitPending,
which calls .values() on the map from task id to host name and iterates through them to see
if any of the tasks are in commit pending. It would be better to have a commit pending boolean
flag in the TaskInProgress. It also looks like there are other opportunities here, but those
jumped out at me. We should also look at this method in the profiler.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message