[
https://issues.apache.org/jira/browse/TAJO-540?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13973744#comment-13973744
]
Hyunsik Choi edited comment on TAJO-540 at 4/18/14 3:11 AM:
------------------------------------------------------------
Hi Min,
After TAJO-752, I'd like to comment out Yarn related code in a subtask.
In addition to TAJO-603, I'd like to actively participate in this work. Also, I
propose making another branch for this work and its subtasks. In the branch, we
can freely do this work and we would not concern with the broken or
completeness of features while we doing it.
It is just a question. Will you reuse some of the exiting Sparrow source code
or implement it in the from-the-scratch manner?
Also, I think that this issue may include as follows:
* Refactoring Worker containers
** Implementing Task Queues/node monitor in Worker
* Refactoring RPC APIs among QueryMaster, TajoMaster, and Workers
* Implementing Sparrow-like scheduler in QueryMaster
Especially, Worker and RPC APIs are deeply related to other parts, and their
codes are somewhat messy. If you are Ok, I'd like to firstly start the
refactoring of worker and RPC APIs in order to help you easily do this work.
What do you think about that?
Best regards,
Hyunsik
was (Author: hyunsik):
Min,
After TAJO-752, I'd like to comment out Yarn related code in a subtask.
In addition to TAJO-603, I'd like to actively participate in this work. Also, I
propose making another branch for this work and its subtasks. In the branch, we
can freely do this work and we would not concern with the broken or
completeness of features while we doing it.
It is just a question. Will you reuse some of the exiting Sparrow source code
or implement it in the from-the-scratch manner?
Also, I think that this issue may include as follows:
* Refactoring Worker containers
** Implementing Task Queues/node monitor in Worker
* Refactoring RPC APIs among QueryMaster, TajoMaster, and Workers
* Implementing Sparrow-like scheduler in QueryMaster
Especially, Worker and RPC APIs are deeply related to other parts, and their
codes are somewhat messy. If you are Ok, I'd like to firstly start the
refactoring of worker and RPC APIs in order to help you easily do this work.
What do you think about that?
Best regards,
Hyunsik
> (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
> Fix For: 0.9
>
>
> 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.2#6252)
