[
https://issues.apache.org/jira/browse/TAJO-540?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13900153#comment-13900153
]
Min Zhou commented on TAJO-540:
-------------------------------
[~jihoonson]
Seems TajoWorkerResourceManager.WorkerResourceAllocationThread.chooseWorkers()
try to solve the problem which kind of resource, memory or disk, is more
critical to the container's requirement, right?
Do you know how yarn solve it? Here is a paper which is used in yarn's all
kind of scheduler
http://www.cs.berkeley.edu/~matei/papers/2011/nsdi_drf.pdf
> (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
> Assignee: Min Zhou
>
> 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.1.5#6160)
