Mailing-List: contact dev-help@kylin.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@kylin.apache.org
Date: Thu, 7 Jul 2016 15:49:11 +0000 (UTC)
From: "Richard Calaba (JIRA)" <jira@apache.org>
To: dev@kylin.apache.org
Message-ID: <JIRA.12987517.1467906503000.49221.1467906551028@Atlassian.JIRA>
In-Reply-To: <JIRA.12987517.1467906503000@Atlassian.JIRA>
References: <JIRA.12987517.1467906503000@Atlassian.JIRA> <JIRA.12987517.1467906503455@arcas>
Subject: [jira] [Created] (KYLIN-1857) Show available memory on UI - in
 System Tab (and other runtime statistics)
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Thu, 07 Jul 2016 15:49:12 -0000

Richard Calaba created KYLIN-1857:
-------------------------------------

             Summary: 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
(v6.3.4#6332)