You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@kylin.apache.org by "nichunen (Jira)" <ji...@apache.org> on 2019/10/30 09:25:00 UTC
[jira] [Closed] (KYLIN-1857) Show available memory on UI - in
System Tab (and other runtime statistics)
[ https://issues.apache.org/jira/browse/KYLIN-1857?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
nichunen closed KYLIN-1857.
---------------------------
Resolution: Fixed
> Show available memory on UI - in System Tab (and other runtime statistics)
> --------------------------------------------------------------------------
>
> Key: KYLIN-1857
> URL: https://issues.apache.org/jira/browse/KYLIN-1857
> Project: Kylin
> Issue Type: Improvement
> Affects Versions: v1.5.2, v1.5.2.1
> Reporter: Richard Calaba
> Priority: Minor
>
> I have run into situation that Kylin dies (exception in log says heap out of memory) if I try to run 3 parallel cubes with high-cardinality dimensions. It is reproduceable scenario. I have set max snapshot size to 2GB and -Xmx to 16GB.
> If I run the cube build one-by-one -> Kylin doesn't die.
> As we have have no idea about memory requirements before we start building the cube(s) then for now it would be beneficial at least to monitor basic Kylin VM statistics, i.e.:
> -- current memory occupied by snaphots
> -- total memory allocation & total free memory
> -- how many (and which) temporary (intermediate) objects (in hive/hbase/filesystem) are created ...
--
This message was sent by Atlassian Jira
(v8.3.4#803005)