[jira] [Resolved] (TUBEMQ-442) Modifying the jvm parameters when the broker starts does not take effect

["Guocheng Zhang (Jira)" <ji...@apache.org>]

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

Guocheng Zhang resolved TUBEMQ-442.
-----------------------------------
    Fix Version/s: 0.8.0
       Resolution: Fixed

> 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
>              Labels: pull-request-available
>             Fix For: 0.8.0
>
>         Attachments: image-2020-12-04-10-59-09-079.png
>
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> 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)