Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update mqbroker to use runbroker.sh instead of runserver.sh when enabling --enable-proxy #7150

Merged
merged 1 commit into from
Aug 17, 2023

Conversation

iamgd67
Copy link
Contributor

@iamgd67 iamgd67 commented Aug 10, 2023

Which Issue(s) This PR Fixes

no issue

Brief Description

Update mqbroker to use runbroker.sh instead of runserver.sh when enabling --enable-proxy this allow JVM heap and gc configuration using broker's settings instead of other common serverices'(proxy,namenode, etc). our main purpose, like the filename mqbroker suggest, is to start broker (which embeds a proxy), so use broker's config is reasonable

chinese version
mqbroker的--enable-proxy选项是启动内嵌了proxy的broker,而不是内嵌broker的proxy,而且broker的工作量和重要程度大于proxy,所以使用broker的gc和heap配置更合适

How Did You Test This Change?

after the change, started broker using configs in runbroker.sh and work well

…--enable-proxy

Update mqbroker to use runbroker.sh instead of runserver.sh when enabling `--enable-proxy`
this allow JVM `heap` and `gc` configuration using broker's settings instead of other common serverices'(proxy,namenode, etc).
our main purpose, like the filename `mqbroker` suggest, is to start broker (which embeds a proxy), so use broker's config is reasonable

chinese version
mqbroker的--enable-proxy选项是启动内嵌了proxy的broker,而不是内嵌broker的proxy,而且broker的工作量和重要程度大于proxy,所以使用broker的gc和heap配置更合适
@iamgd67 iamgd67 changed the title Update mqbroker to use runbroker.sh instead of runserver.sh when use --enable-proxy Update mqbroker to use runbroker.sh instead of runserver.sh when enabling --enable-proxy Aug 10, 2023
@iamgd67
Copy link
Contributor Author

iamgd67 commented Aug 11, 2023

@xdkxlk
Looks like some checks have been hung for 17 hourse. Can you retrigger them?

@iamgd67
Copy link
Contributor Author

iamgd67 commented Aug 15, 2023

@xdkxlk cleaned commit history, can you trigger the workflows?

@xdkxlk
Copy link
Contributor

xdkxlk commented Aug 15, 2023

@xdkxlk cleaned commit history, can you trigger the workflows?

OK

@codecov-commenter
Copy link

codecov-commenter commented Aug 15, 2023

Codecov Report

Merging #7150 (c2ba8fa) into develop (99b39a3) will increase coverage by 0.12%.
Report is 7 commits behind head on develop.
The diff coverage is n/a.

@@              Coverage Diff              @@
##             develop    #7150      +/-   ##
=============================================
+ Coverage      42.12%   42.24%   +0.12%     
- Complexity      9260     9413     +153     
=============================================
  Files           1149     1149              
  Lines          82033    83176    +1143     
  Branches       10699    10858     +159     
=============================================
+ Hits           34554    35137     +583     
- Misses         43129    43667     +538     
- Partials        4350     4372      +22     

see 29 files with indirect coverage changes

📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more

@iamgd67
Copy link
Contributor Author

iamgd67 commented Aug 17, 2023

@xdkxlk are we ready to merge this or waiting for more reviews

@xdkxlk xdkxlk merged commit 2b93e1e into apache:develop Aug 17, 2023
@iamgd67 iamgd67 deleted the iamgd67-patch-1 branch October 19, 2023 08:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants