tajo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "hyoungjunkim (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (TAJO-158) Can't allocate worker when single SubQuery requests more than cluster capacity.
Date Thu, 05 Sep 2013 01:30:52 GMT

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

hyoungjunkim updated TAJO-158:
------------------------------

    Attachment: TAJO-158.patch

In current implementation TajoResourceManager reuses async RPC call back function. 
Tajo's async RPC call back function is one time function.
                
> 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

Mime
View raw message