You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@tajo.apache.org by "Min Zhou (JIRA)" <ji...@apache.org> on 2014/03/24 19:22:50 UTC

[jira] [Updated] (TAJO-603) Move container allocation from SubQuery down to QueryUnitAttempt

     [ https://issues.apache.org/jira/browse/TAJO-603?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Min Zhou updated TAJO-603:
--------------------------

    Assignee: Hyunsik Choi  (was: Min Zhou)

> 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)