You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@zookeeper.apache.org by "zhanglu153 (Jira)" <ji...@apache.org> on 2023/05/31 06:03:00 UTC
[jira] [Created] (ZOOKEEPER-4701) Unable to use other JVM memory options to control zookeeper memory usage.
zhanglu153 created ZOOKEEPER-4701:
-------------------------------------
Summary: Unable to use other JVM memory options to control zookeeper memory usage.
Key: ZOOKEEPER-4701
URL: https://issues.apache.org/jira/browse/ZOOKEEPER-4701
Project: ZooKeeper
Issue Type: Improvement
Components: scripts
Affects Versions: 3.8.1, 3.7.1, 3.8.0, 3.6.2, 3.5.8, 3.6.1, 3.5.7, 3.5.6, 3.5.5, 3.7.0, 3.6.3, 3.6.0, 3.5.4, 3.5.3, 3.5.2, 3.5.1, 3.5.0, 3.5.10, 3.5.9, 3.6.4
Reporter: zhanglu153
After upgrading from version 3.4.14 to version 3.6.4, it was found that other JVM memory options such as - XX: MaxRAMPercentage cannot be used to control the memory usage of zookeeper. Upon investigation, it was found that the reason was due to the addition of a default setting for heap size in the zkEnv.sh script in version 3.5, with a default value of 1000M.
{code:java}
ZK_SERVER_HEAP="${ZK_SERVER_HEAP:-1000}"
export SERVER_JVMFLAGS="-Xmx${ZK_SERVER_HEAP}m $SERVER_JVMFLAGS"{code}
When the user uses - XX: MaxRAMPercentage to control the memory usage of zookeeper, it is found that the memory configuration will be overwritten by the default - Xmx configuration value. This does not meet the memory usage configuration required by the user.
In Zookeeper-4391, it is also proposed to add a flag to disable the memory configuration behavior by default. This default value can only be optionally released when users need to use the default heap size configuration.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)