[
https://issues.apache.org/jira/browse/TAJO-540?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13892877#comment-13892877
]
Min Zhou commented on TAJO-540:
-------------------------------
I'd like to write more about the code implementation.
Currently, tajo has 2 threads for sheduling. One which is standalone mode
schedules queries by tajo itself, the other is yarn mode where queries
resources are allocated by a yarn cluster.
Regarding to the standalone mode. When TajoMaster receives a query, it firstly
use TajoWorkerResourceManager to choose a idler QueryMaster for this query.
Then the query will be sent to that QueryMaster. QueryMaster breaks the query
into several execution blocks, each execution block consists of several
tasks. TajoResourceAllocator reside in that QueryMaster send a rpc call
TajoMasterProtocol.allocateWorkerResources() to TajoMaster. TajoMaster then use
TajoWorkerResourceManager again to allocate workers for execution block. Yarn
mode is quite similar.
What we want to do some change is for the standalone mode, right?
> (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.1.5#6160)
