[
https://issues.apache.org/jira/browse/TAJO-1130?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14370489#comment-14370489
]
ASF GitHub Bot commented on TAJO-1130:
--------------------------------------
Github user hyunsik commented on the pull request:
https://github.com/apache/tajo/pull/423#issuecomment-83835137
We need to be eager to fix the problems for SNAPSHOT term. If we face some
very critical issues to interrupt other developments, we can disable it by
default at that time.
Also, I think that this feature will have the following problem in the
current implementation:
* Resource allocation will be performed once when ExecutionBlock starts,
and the allocated resources won't be changed during the execution block.
* It means that some execution block can be slow if the execution starts
with few resource capacity.
TAJO-1397 (https://issues.apache.org/jira/browse/TAJO-1397) will solve this
problem, enabling continuous resource allocation while an execution block is
running. I'll rush this issue.
> Concurrent execution of independent execution blocks
> -----------------------------------------------------
>
> Key: TAJO-1130
> URL: https://issues.apache.org/jira/browse/TAJO-1130
> Project: Tajo
> Issue Type: Improvement
> Components: query master
> Reporter: Jihoon Son
> Assignee: Navis
>
> Currently, Tajo can execute ExecutionBlocks one by one even though there
> remain enough resources to execute two or more ExecutionBlocks.
> We can improve the query processing performance by executing two or more
> independent ExecutionBlocks if possible.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
