saz97 opened a new pull request, #9549: URL: https://github.com/apache/rocketmq/pull/9549
The route update mechanism in RocketMQ currently relies on a periodic polling approach by Clients and Proxy. This passive update mechanism causes some issues during route events (e.g., master/slave switch, Broker shutdown): 1. Clients persistently use outdated routing information, leading to write failures when sending requests to deactivated Brokers 2. Connections to destroyed IP addresses result in complete communication breakdown 3. New resources cannot be promptly utilized for load balancing Fundamentally, operations during polling intervals rely on incorrect routing decisions, compromising service high availability. To address this, I would like to start an email thread to discuss the RIP-79 Route Change Notification, reconstructing the route synchronization mechanism to achieve event-driven route state synchronization. The redesigned architecture can resolves untimely route updates: Clients no longer connect to invalid nodes, eliminating service interruptions during master/slave switches, and new resources can be immediately discovered and leveraged. Additionally, redundant query pressure on NameServer is reduced through merged update requests and a lazy update policy. Relevant work is already in progress. Proposal documentation is available here: https://docs.google.com/document/d/1iMQQ0wDO4dULGpjsKyq6kCbcsUL0JjNcii-KbM90a18/edit?usp=sharing -- 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 For queries about this service, please contact Infrastructure at: us...@infra.apache.org
