[
https://issues.apache.org/jira/browse/TUBEMQ-442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17243666#comment-17243666
]
Guocheng Zhang commented on TUBEMQ-442:
---------------------------------------
!image-2020-12-04-10-59-09-079.png!
This problem is a clerical error. TubeMQ is used in very large-scale scenarios,
Master and Broker are rarely deployed in one machine, even if they are deployed
in one, there is no performance problem, so this problem has not been found.
thank! [~leno]
> Modifying the jvm parameters when the broker starts does not take effect
> ------------------------------------------------------------------------
>
> Key: TUBEMQ-442
> URL: https://issues.apache.org/jira/browse/TUBEMQ-442
> Project: Apache TubeMQ
> Issue Type: Bug
> Components: Server
> Reporter: xianle cao
> Assignee: Guocheng Zhang
> Priority: Major
> Attachments: image-2020-12-04-10-59-09-079.png
>
>
> When the master and broker are deployed on the same machine, modify the
> BROKER_JVM_SIZE parameter in the bin/env.sh file, the parameter does not take
> effect.
> ```
> cat bin/env.sh
> if [ -z "$MASTER_JVM_SIZE" ]; then
> MASTER_JVM_SIZE="-Xmx10g -Xms6g"
> fi
> MASTER_JVM_ARGS="$MASTER_JVM_SIZE -server -Dtubemq.home=$tubemq_home -cp
> $CLASSPATH "
> #Broker jvm args
> if [ -z "$MASTER_JVM_SIZE" ]; then
> BROKER_JVM_SIZE="-Xmx12g -Xms12g -Xmn4g"
> fi
> ```
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
