You are viewing a plain text version of this content. The canonical link for it is here.

Posted to mapreduce-issues@hadoop.apache.org by "Xiao Kang (JIRA)" <ji...@apache.org> on 2010/04/08 12:10:36 UTC

[jira] Commented: (MAPREDUCE-1684) ClusterStatus can be cached in CapacityTaskScheduler.assignTasks()

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

Xiao Kang commented on MAPREDUCE-1684:
--------------------------------------

What's the reason to cache ClusterStatus, performance improvement?

> 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: contrib/capacity-sched
>            Reporter: Amareshwari Sriramadasu
>
> 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.
-
You can reply to this email to add a comment to the issue online.