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

Posted to issues@zookeeper.apache.org by "Frederiko Costa (Jira)" <ji...@apache.org> on 2024/01/30 05:43:00 UTC

[jira] [Updated] (ZOOKEEPER-4797) Allow for -XX:MaxRAMPercentage JVM setting

     [ https://issues.apache.org/jira/browse/ZOOKEEPER-4797?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Frederiko Costa updated ZOOKEEPER-4797:
---------------------------------------
    Summary: Allow for -XX:MaxRAMPercentage JVM setting  (was: Allow for -XX:MaxRamPercentage JVM setting)

> Allow for -XX:MaxRAMPercentage JVM setting
> ------------------------------------------
>
>                 Key: ZOOKEEPER-4797
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-4797
>             Project: ZooKeeper
>          Issue Type: Improvement
>          Components: scripts
>            Reporter: Frederiko Costa
>            Priority: Major
>
> When running Zk in a containerized environment, it's sometimes desirable to express your heap size in terms of percentage of available memory allocated to a container.
> As it stands, zkEnv.sh forces your to have  -Xmx, which defaults to 1GB. Some environments wanted to set it to more, mostly related to the amount of Ram.
> This is a request to implement the option of using -XX:MaxRamPercentage option when starting zookeeper.
> Suggested implementation is to also make a variable ZK_SERVER_MAXRAMPERCENTAGE available to be added to SERVER_JVMFLAGS. If the variable is set, ZK_HEAP_SERVER is ignored, if no ZK_SERVER_MAXRAMPERCENTAGE, ZK_SERVER_HEAP is set as usual.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)