[
https://issues.apache.org/jira/browse/TAJO-603?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13955704#comment-13955704
]
Min Zhou commented on TAJO-603:
-------------------------------
Hi Jihoon & Hyunsik
As I said offline, the purpose for this ticket is just for simplify the
container allocation, not insisted to move the allocation from SubQuery down
to QueryUnitAttempt. It's was just my thought if we take that movement , the
code will get simpler.
If you think that there is another way for this purpose, please go ahead. and
please feel free to show your opinion on this issue.
> Move container allocation from SubQuery down to QueryUnitAttempt
> ----------------------------------------------------------------
>
> Key: TAJO-603
> URL: https://issues.apache.org/jira/browse/TAJO-603
> Project: Tajo
> Issue Type: Sub-task
> Reporter: Min Zhou
> Assignee: Hyunsik Choi
> Fix For: 1.0-incubating
>
> Attachments: schedule.png
>
>
> Tajo currently allocates all of the containers in SubQuery. That make things
> complicated. Both SubQuery and DefaultTaskScheduler should hold a copy of
> allocated containers and running tasks. And the event flow is difficult to
> understand.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
