hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Wangda Tan (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-3026) Move application-specific container allocation logic from LeafQueue to FiCaSchedulerApp
Date Thu, 23 Jul 2015 17:24:05 GMT

    [ https://issues.apache.org/jira/browse/YARN-3026?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14639171#comment-14639171
] 

Wangda Tan commented on YARN-3026:
----------------------------------

I tried to run failed tests locally with the patch, both can be passed.

> Move application-specific container allocation logic from LeafQueue to FiCaSchedulerApp
> ---------------------------------------------------------------------------------------
>
>                 Key: YARN-3026
>                 URL: https://issues.apache.org/jira/browse/YARN-3026
>             Project: Hadoop YARN
>          Issue Type: Task
>          Components: capacityscheduler
>            Reporter: Wangda Tan
>            Assignee: Wangda Tan
>         Attachments: YARN-3026.1.patch, YARN-3026.2.patch, YARN-3026.3.patch, YARN-3026.4.patch
>
>
> Have a discussion with [~vinodkv] and [~jianhe]: 
> In existing Capacity Scheduler, all allocation logics of and under LeafQueue are located
in LeafQueue.java in implementation. To make a cleaner scope of LeafQueue, we'd better move
some of them to FiCaSchedulerApp.
> Ideal scope of LeafQueue should be: when a LeafQueue receives some resources from ParentQueue
(like 15% of cluster resource), and it distributes resources to children apps, and it should
be agnostic to internal logic of children apps (like delayed-scheduling, etc.). IAW, LeafQueue
shouldn't decide how application allocating container from given resources.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message