[
https://issues.apache.org/jira/browse/MAPREDUCE-1684?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12855509#action_12855509
]
Vinod K V commented on MAPREDUCE-1684:
--------------------------------------
bq. What's the reason to cache ClusterStatus, performance improvement?
Yes. Currently obtaining the ClusterStatus object needs the petrifying global
JT lock.
> 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.
