[
https://issues.apache.org/jira/browse/ROCKETMQ-161?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15952197#comment-15952197
]
ASF GitHub Bot commented on ROCKETMQ-161:
-----------------------------------------
GitHub user dongeforever opened a pull request:
https://github.com/apache/incubator-rocketmq/pull/87
[ROCKETMQ-161] Update runbroker.sh and runserver.sh to support user defined
jvm mem flag
https://issues.apache.org/jira/browse/ROCKETMQ-161?filter=-1
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/dongeforever/incubator-rocketmq ROCKETMQ-161
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/incubator-rocketmq/pull/87.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #87
----
commit 23e14efd07f0e68b52d139053f0c94043164efda
Author: dongeforever <[email protected]>
Date: 2017-04-01T12:26:36Z
[ROCKETMQ-161] Update runbroker.sh and runserver.sh to support user defined
jvm memory flag
----
> 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
>
> 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)
