You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@asterixdb.apache.org by "Wenhai (JIRA)" <ji...@apache.org> on 2016/05/13 17:41:12 UTC
[jira] [Commented] (ASTERIXDB-1442) Global memory management is
required
[ https://issues.apache.org/jira/browse/ASTERIXDB-1442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15282905#comment-15282905 ]
Wenhai commented on ASTERIXDB-1442:
-----------------------------------
We encountered similar problems. Once we configured 50GB for nc.java.opts and 40GB for buffercache, we almost always got a dead NC error even when we only load the datasets.
> 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
>
> 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)