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

Jinho Kim edited comment on TAJO-540 at 12/10/14 2:14 AM:
----------------------------------------------------------

Hello guys

Recently I’m looking a solution for capacity scheduler on WorkerNode. But it is 
very difficult and many challenges to me. 
Jihoon suggested omega scheduler to me. It very interesting and will be help to 
implement our scheduler
http://research.google.com/pubs/pub41684.html

As first, I suggest to borrow yarn scheduler queue into Tajo. It will be easy 
to add the multi-tenant query scheduler
What do you think about to borrow the yarn scheduler queue for initial 
implementation?


was (Author: jhkim):
Hello guys

Recently I’m looking a solution for capacity scheduler on WorkerNode. But it is 
very difficult and many challenges to me. 
Jihoon suggested omega scheduler to me. It very interesting and will be help to 
implement our scheduler
http://research.google.com/pubs/pub41684.html

As first, I suggest to port yarn scheduler into Tajo. It will be easy to add 
the multi-tenant query scheduler
What do you think about to port the yarn scheduler for initial implementation?

> (Umbrella) Implement Tajo Query Scheduler
> -----------------------------------------
>
>                 Key: TAJO-540
>                 URL: https://issues.apache.org/jira/browse/TAJO-540
>             Project: Tajo
>          Issue Type: New Feature
>            Reporter: Hyunsik Choi
>
> Currently, there is no Tajo query scheduler. So, all queries launched 
> simultaneously compete cluster resource which is managed by 
> TajoResourceManager.
> In this issue, we will investigate,  design, and implement a Tajo query 
> scheduler. This is an umbrella issue for that. We will create subtasks for 
> them.



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

Reply via email to