[
https://issues.apache.org/jira/browse/MAPREDUCE-529?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12916766#action_12916766
]
Greg Roelofs commented on MAPREDUCE-529:
----------------------------------------
Sorry, that should have said fixed via HADOOP-4980, not 6980.
> Code to create the UI display string for queues in the Capacity Scheduler
> needs to be synchronized, and needs to better update its information
> ----------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: MAPREDUCE-529
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-529
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Reporter: Vivek Ratan
>
> There are a couple of problems with _SchedulingInfo.toString()_, the code
> which creates the UI display string for a queue:
> * it needs synchronized access to the _QueueSchedulingInfo_ object, as this
> same object can be updated by the reclaim-capacity thread, and during a
> heartbeat.
> * the code directly updates its count of running map/reduce tasks. this
> should be done in a better way, perhaps by calling updateQSIObjects(), rather
> than walking through the data structures directly. It's also not clear that
> we want to pay the performance penalty of updating the structures. it maybe
> OK to provide slightly stale info (the 'staleness' is tiny, in a steady-state
> and large system, where heartbeats are coming in frequently).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
