hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Djellel Eddine Difallah (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (YARN-897) CapacityScheduler wrongly sorted queues
Date Thu, 11 Jul 2013 20:23:48 GMT

     [ https://issues.apache.org/jira/browse/YARN-897?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Djellel Eddine Difallah updated YARN-897:
-----------------------------------------

    Attachment: YARN-897-1.patch

Attached is a first patch attempt to address the bug:
Upon container completion, which triggers completedContainer(), remove and reinsert the queue
into its parent's childQueues. This operation is done recursively starting from the leafQueue
where the container got released. 
Thus, by handling both cases where usedCapacity is ever changed (assignement and completion)
the TreeSet remains properly sorted.
                
> CapacityScheduler wrongly sorted queues
> ---------------------------------------
>
>                 Key: YARN-897
>                 URL: https://issues.apache.org/jira/browse/YARN-897
>             Project: Hadoop YARN
>          Issue Type: Bug
>          Components: capacityscheduler
>            Reporter: Djellel Eddine Difallah
>         Attachments: TestBugParentQueue.java, YARN-897-1.patch
>
>
> The childQueues of a ParentQueue are stored in a TreeSet where UsedCapacity defines the
sort order. This ensures the queue with least UsedCapacity to receive resources next. On containerAssignment
we correctly update the order, but we miss to do so on container completions. This corrupts
the TreeSet structure, and under-capacity queues might starve for resources.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message