tajo-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hyunsik Choi (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (TAJO-603) Move container allocation from SubQuery down to QueryUnitAttempt
Date Wed, 02 Apr 2014 18:09:18 GMT

    [ https://issues.apache.org/jira/browse/TAJO-603?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13957966#comment-13957966
] 

Hyunsik Choi edited comment on TAJO-603 at 4/2/14 6:09 PM:
-----------------------------------------------------------

Hi [~coderplay],

I'm sorry for my delayed work on this issue. I'm concerning that my delay may affect your
work. I'll describe my plan on this issue within few days.


was (Author: hyunsik):
Hi [~coderplay]

I'm sorry for my delayed work on this issue. I'm concerning that my delay may affect your
work. I'll describe my plan on this issue within few days.

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

Mime
View raw message