You are viewing a plain text version of this content. The canonical link for it is here.
Posted to yarn-issues@hadoop.apache.org by "Wangda Tan (JIRA)" <ji...@apache.org> on 2015/01/09 22:39:34 UTC
[jira] [Created] (YARN-3026) Move application-specific container
allocation logic from LeafQueue to FiCaSchedulerApp
Wangda Tan created YARN-3026:
--------------------------------
Summary: 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
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)