yx9o opened a new issue, #9115: URL: https://github.com/apache/rocketmq/issues/9115
### Before Creating the Enhancement Request - [X] I have confirmed that this should be classified as an enhancement rather than a bug/feature. ### Summary Hi, community This is a reverse notification issue triggered by broker for consumerId change. ### Motivation We encountered such a problem in the online environment: An application has 100+ clients, and each client has multiple group subscriptions. When the application is released, any node will trigger a large number of reverse notifications. When the threshold is exceeded, most of the notifications fail, and we only need the latest notification. ### Describe the Solution You'd Like Our idea is to improve the real-time notification part. If there are new channels that need to be notified in the same group, we will stop the last notification and always notify with the latest channels. ### Describe Alternatives You've Considered Stop the broker's reverse notification and downgrade to the client's own balance logic processing. ### Additional Context _No response_ -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: commits-unsubscr...@rocketmq.apache.org.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
