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

Taewoo Kim edited comment on ASTERIXDB-1442 at 8/10/16 10:22 PM:
-----------------------------------------------------------------

Additional comment from ASTERIXDB-1556 discussion: 

#4. Query Sanity Check should be done. After a physical plan is computed, we 
can calculate the maximum memory usage per operators in each stage. So, the 
impossible execution of a query based on the global memory setting can be 
checked and safely ignored rather than executing an Out Of Memory exception 
error.


was (Author: wangsaeu):
Additional comment from ASTERIXDB-1566 discussion: 

#4. Query Sanity Check should be done. After a physical plan is computed, we 
can calculate the maximum memory usage per operators in each stage. So, the 
impossible execution of a query based on the global memory setting can be 
checked and safely ignored rather than executing an Out Of Memory exception 
error.

> Global memory management is required
> ------------------------------------
>
>                 Key: ASTERIXDB-1442
>                 URL: https://issues.apache.org/jira/browse/ASTERIXDB-1442
>             Project: Apache AsterixDB
>          Issue Type: Improvement
>            Reporter: Taewoo Kim
>            Assignee: Michael Blow
>
> We set a few memory usage related parameter such as sort-memory, group-memory 
> and join-memory in asterix-configuration.xml. There are a few more parameters 
> as well. An issue is that each parameter is used individually by Asterix 
> codebase and there is no global management regarding these parameters. 
> Thus, for example, we can't guard a situation where memory allocation of sub 
> components such as sort-memory and group-memory is greater than the NC java 
> heap size.
> It would be really nice if we have a query memory budgeting feature, too. If 
> it is evident that a query will exceed certain memory budget, we can warn 
> users rather than issuing runtime Out Of Memory error.
>   



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to