You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tajo.apache.org by "Hyunsik Choi (JIRA)" <ji...@apache.org> on 2013/09/05 03:57:52 UTC
[jira] [Commented] (TAJO-158) Can't allocate worker when single
SubQuery requests more than cluster capacity.
[ https://issues.apache.org/jira/browse/TAJO-158?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13758664#comment-13758664 ]
Hyunsik Choi commented on TAJO-158:
-----------------------------------
+1
The patch looks good for me.
> Can't allocate worker when single SubQuery requests more than cluster capacity.
> -------------------------------------------------------------------------------
>
> Key: TAJO-158
> URL: https://issues.apache.org/jira/browse/TAJO-158
> Project: Tajo
> Issue Type: Bug
> Components: resource manager
> Affects Versions: 0.2-incubating
> Reporter: hyoungjunkim
> Assignee: hyoungjunkim
> Priority: Critical
> Attachments: TAJO-158.patch
>
>
> In standby mode, QueryMaster requests to Tajo's ResourceManager.
> If single SubQuery requests more than cluster capacity, That SubQuery doesn't receive worker resource forever.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira