-
Notifications
You must be signed in to change notification settings - Fork 113
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
[ISSUE #2234]⚡️Optimize BrokerRuntimeInner register_broker_all method paramters🦺 #2235
Conversation
WalkthroughThe pull request introduces enhancements to the broker registration process in RocketMQ's Rust implementation. The changes modify the Changes
Assessment against linked issues
Possibly related PRs
Suggested labels
Suggested reviewers
Poem
Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media? 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
Documentation and Community
|
🔊@mxsm 🚀Thanks for your contribution🎉! 💡CodeRabbit(AI) will review your code first🔥! Note 🚨The code review suggestions from CodeRabbit are to be used as a reference only, and the PR submitter can decide whether to make changes based on their own judgment. Ultimately, the project management personnel will conduct the final code review💥. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actionable comments posted: 0
🧹 Nitpick comments (1)
rocketmq-common/src/common/broker/broker_config.rs (1)
200-201
: Add documentation for the new configuration fields.The new fields look good, but please add documentation to explain:
- Purpose and impact of enabling
compressed_register
- Expected values and behavior for
broker_not_active_timeout_millis
+ /// Whether to compress broker registration data to reduce network bandwidth usage. pub compressed_register: bool, + /// Timeout in milliseconds after which a broker is considered inactive. + /// Only used when `enable_slave_acting_master` is true. pub broker_not_active_timeout_millis: i64,
📜 Review details
Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (2)
rocketmq-broker/src/broker_runtime.rs
(1 hunks)rocketmq-common/src/common/broker/broker_config.rs
(2 hunks)
⏰ Context from checks skipped due to timeout of 90000ms (9)
- GitHub Check: build (windows-latest, nightly)
- GitHub Check: build (windows-latest, stable)
- GitHub Check: build (macos-latest, nightly)
- GitHub Check: build (macos-latest, stable)
- GitHub Check: test
- GitHub Check: build (ubuntu-latest, nightly)
- GitHub Check: build (ubuntu-latest, stable)
- GitHub Check: build
- GitHub Check: auto-approve
🔇 Additional comments (2)
rocketmq-common/src/common/broker/broker_config.rs (1)
304-305
: LGTM! Default values look reasonable.
compressed_register
defaults tofalse
which maintains backward compatibilitybroker_not_active_timeout_millis
defaults to 10 seconds which is a typical network timeout valuerocketmq-broker/src/broker_runtime.rs (1)
1096-1102
: LGTM! Registration parameters are now properly configurable.The changes improve the broker registration process by:
- Using configurable timeout from
register_broker_timeout_mills
- Supporting compressed registration via
compressed_register
- Conditionally setting inactive broker timeout only when slave is acting as master
Run this script to verify the integration:
✅ Verification successful
Broker registration parameters are properly integrated and used
The verification confirms that:
- Registration timeout is properly configured and passed through
- Compressed registration is correctly integrated
- Inactive broker timeout is correctly applied only when slave is acting as master
🏁 Scripts executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash # Description: Verify the usage of new broker registration parameters. # Test 1: Check if the new parameters are used consistently rg -A 5 'register_broker_all.*compressed_register' # Test 2: Check if the timeout is used correctly rg -A 5 'register_broker_timeout_mills' # Test 3: Check if the inactive timeout is used correctly rg -A 5 'broker_not_active_timeout_millis.*enable_slave_acting_master'Length of output: 2876
Script:
#!/bin/bash # Search for compressed_register configuration and usage rg "compressed_register" -A 3 # Search for broker_not_active_timeout_millis rg "broker_not_active_timeout_millis" -A 3 # Find the registration method implementation ast-grep --pattern 'fn do_register_broker_all($$$) { $$$ }'Length of output: 2017
Script:
#!/bin/bash # Find the registration method and its parameter usage rg -A 10 "async fn register_broker_all" # Find where these parameters are used in the registration process ast-grep --pattern 'register_broker_all($$$) -> $$ { $$$ }'Length of output: 2679
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #2235 +/- ##
=======================================
Coverage 28.32% 28.32%
=======================================
Files 498 498
Lines 72150 72154 +4
=======================================
+ Hits 20435 20437 +2
- Misses 51715 51717 +2 ☔ View full report in Codecov by Sentry. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Which Issue(s) This PR Fixes(Closes)
Fixes #2234
Brief Description
How Did You Test This Change?
Summary by CodeRabbit
New Features
Configuration Updates