Conversation
…o parameter is configured for the brokerStatus command.(apache#5818)
…ata of the subscription group on the standby node, when execute command 'mqadmin deleteSubGroup -b xxx -g xxx -r true'.
…n the standby node, when execute command 'mqadmin deleteTopic -b xxx -t xxx to delete unused topic'.
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## develop #7273 +/- ##
=============================================
- Coverage 48.85% 48.75% -0.10%
+ Complexity 12769 12745 -24
=============================================
Files 1324 1324
Lines 96405 96409 +4
Branches 12434 12434
=============================================
- Hits 47094 47008 -86
- Misses 43568 43642 +74
- Partials 5743 5759 +16 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
joeCarf
left a comment
There was a problem hiding this comment.
I think the title might be too long, suggest renaming [ISSUE xx& ISSUE xxx] Fix: xxx
|
lgtm this bothers me too. I copy master's consumerqueue data to slave and restart slave to fix |
|
seek for integration |
@ joeCarf It's been changed. Please submit it,Thanks |
@joeCarf seek for integration |
|
Begging to join |
|
@mxsm @Oliverwqcwrw Help to integrate the code. |
|
lgtm |
|
seek for integration |
|
@ joeCarf @ iamgd67 review again |
|
lgtm, but I am not a commiter, don't have perge permission. |
|
seek for integration |
RockteMQ-AI
left a comment
There was a problem hiding this comment.
Summary
This PR fixes two issues in SlaveSynchronize for slave broker synchronization:
- Missing
cleanUnusedTopic()call — When topic config changes on the slave, stale topics should be cleaned. The fix addscleanUnusedTopic()before syncing the new config. - Consumer offset table not cleared before sync — Without clearing, old offsets from a previous master could persist alongside new ones, causing incorrect offset data. The fix clears the table before
putAll().
The logic is sound. However, this PR targets develop from develop (same branch), which is unusual. The head branch should ideally be a feature branch. Also, this PR is 3+ years old — the codebase may have evolved. A rebase and fresh test run would be advisable before merging.
Automated review by github-manager-bot
Which Issue(s) This PR Fixes
Fixes #7263 and #7264
Brief Description
How Did You Test This Change?