You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@kylin.apache.org by "hongbin ma (JIRA)" <ji...@apache.org> on 2016/07/01 10:59:11 UTC

[jira] [Commented] (KYLIN-1830) Put KYLIN_JVM_SETTINGS to kylin.properties

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

hongbin ma commented on KYLIN-1830:
-----------------------------------

kylin.properties is not read until kylin server JVM is up, so it cannot be used to configure the JVM's VM options

> Put KYLIN_JVM_SETTINGS to kylin.properties
> ------------------------------------------
>
>                 Key: KYLIN-1830
>                 URL: https://issues.apache.org/jira/browse/KYLIN-1830
>             Project: Kylin
>          Issue Type: Improvement
>            Reporter: Richard Calaba
>            Priority: Minor
>
> Currently is the KYLIN_JVM_SETTINGS variable stored in the ,/bin/setenv.sh ... which is not wrong, but as we have also some other memory specific setting in ./conf/kylin.properties file (like i.e kylin.job.mapreduce.default.reduce.input.mb or kylin.table.snapshot.max_mb) it might be good idea to have those performance and sizing related parameters in one location.



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