hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Devaraj Das (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MAPREDUCE-1684) ClusterStatus can be cached in CapacityTaskScheduler.assignTasks()
Date Wed, 15 Aug 2012 21:07:38 GMT

    [ https://issues.apache.org/jira/browse/MAPREDUCE-1684?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13435531#comment-13435531
] 

Devaraj Das commented on MAPREDUCE-1684:
----------------------------------------

Looks good to me.
                
> ClusterStatus can be cached in CapacityTaskScheduler.assignTasks()
> ------------------------------------------------------------------
>
>                 Key: MAPREDUCE-1684
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-1684
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>          Components: capacity-sched
>            Reporter: Amareshwari Sriramadasu
>         Attachments: mapreduce-1684-v1.0.2-1.patch
>
>
> Currently,  CapacityTaskScheduler.assignTasks() calls getClusterStatus() thrice: once
in assignTasks(), once in MapTaskScheduler and once in ReduceTaskScheduler. It can be cached
in assignTasks() and re-used.

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

        

Mime
View raw message