[MAPREDUCE-529] Code to create the UI display string for queues in the Capacity Scheduler needs to be synchronized, and needs to better update its information

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Assignee: Unassigned
• Reporter: Vivek Ratan
• Created: 06/Jan/09 05:42
• Updated: 01/Oct/10 03:20
• Resolved: 01/Oct/10 03:18

Description

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