You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@rocketmq.apache.org by "dongeforever (JIRA)" <ji...@apache.org> on 2017/05/25 08:37:04 UTC
[jira] [Closed] (ROCKETMQ-161) Update runbroker.sh and runserver.sh
to support user defined jvm memory flag
[ https://issues.apache.org/jira/browse/ROCKETMQ-161?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
dongeforever closed ROCKETMQ-161.
---------------------------------
Resolution: Fixed
Github user dongeforever closed the pull request at:
https://github.com/apache/incubator-rocketmq/pull/87
> Update runbroker.sh and runserver.sh to support user defined jvm memory flag
> ----------------------------------------------------------------------------
>
> Key: ROCKETMQ-161
> URL: https://issues.apache.org/jira/browse/ROCKETMQ-161
> Project: Apache RocketMQ
> Issue Type: Improvement
> Reporter: dongeforever
> Assignee: dongeforever
> Fix For: 4.1.0-incubating
>
>
> JVM mem flag is hard coded in runbroker.sh as follows:
> JAVA_OPT="${JAVA_OPT} -server -Xms8g -Xmx8g -Xmn4g"
> If one want to change such flag, he has to change the script, this is not friendly, especially in docker environment.
> Instead, it is able to use an environment variable to handle user defined flag, like:
> if [ -z $BROKER_MEM_OPS ]; then
> BROKER_MEM_OPS = "-Xms8g -Xmx8g -Xmn4g"
> fi
> JAVA_OPT="${JAVA_OPT} -server $BROKER_MEM_OPS"
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)