-
Notifications
You must be signed in to change notification settings - Fork 119
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
[ISSUE #2268]💫Optimize BrokerRuntime start method🧑💻 #2272
Conversation
WalkthroughThe pull request introduces modifications to the RocketMQ broker runtime, focusing on enhancing the broker registration and synchronization processes. A new method 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: 1
📜 Review details
Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (2)
rocketmq-broker/src/broker_runtime.rs
(3 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: build
- GitHub Check: build (ubuntu-latest, nightly)
- GitHub Check: build (ubuntu-latest, stable)
- GitHub Check: auto-approve
- GitHub Check: test
🔇 Additional comments (4)
rocketmq-common/src/common/broker/broker_config.rs (2)
202-202
: LGTM: New configuration field for broker member group synchronization.The new public field
sync_broker_member_group_period
is well-placed in theBrokerConfig
struct and appropriately typed asu64
for storing millisecond values.
307-307
: LGTM: Reasonable default value for synchronization period.The default value of 1,000 milliseconds (1 second) is a reasonable interval for periodic synchronization of broker member groups.
rocketmq-broker/src/broker_runtime.rs (2)
979-1019
: LGTM: Improved broker registration task.The registration task has been optimized with:
- Bounded registration period (10s-60s)
- Proper state checks before registration
- Improved configuration management
1033-1059
: LGTM: Well-structured broker member group sync task.The synchronization task is properly implemented with:
- Conditional execution based on
enable_slave_acting_master
- Configurable period via
sync_broker_member_group_period
- Proper delay calculation for periodic execution
pub fn sync_broker_member_group(&self) { | ||
warn!("sync_broker_member_group not implemented"); | ||
} |
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.
Implement the sync_broker_member_group
method.
The method is currently a placeholder that only logs a warning. Implementation is needed to complete the broker member group synchronization feature.
Would you like me to help implement this method? I can provide a solution that:
- Retrieves the current broker member group
- Synchronizes it with other brokers
- Handles any synchronization failures
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #2272 +/- ##
==========================================
- Coverage 28.25% 28.24% -0.02%
==========================================
Files 504 504
Lines 72320 72358 +38
==========================================
+ Hits 20437 20438 +1
- Misses 51883 51920 +37 ☔ View full report in Codecov by Sentry. |
Which Issue(s) This PR Fixes(Closes)
Fixes #2268
Brief Description
How Did You Test This Change?
Summary by CodeRabbit
New Features
Improvements