RongtongJin opened a new issue #3792: URL: https://github.com/apache/rocketmq/issues/3792
The issue tracker is **ONLY** used for bug report(feature request need to follow [RIP process](https://github.com/apache/rocketmq/wiki/RocketMQ-Improvement-Proposal)). Keep in mind, please check whether there is an existing same report before your raise a new one. Alternately (especially if your communication is not a bug report), you can send mail to our [mailing lists](http://rocketmq.apache.org/about/contact/). We welcome any friendly suggestions, bug fixes, collaboration and other improvements. Please ensure that your bug report is clear and that it is complete. Otherwise, we may be unable to understand it or to reproduce it, either of which would prevent us from fixing the bug. We strongly recommend the report(bug report or feature request) could include some hints as the following: **FEATURE REQUEST** 1. Please describe the feature you are requesting. Nameserver is a very important component in RocketMQ cluster, which is used for route discovery. At present, the nameserver is stateless and lightweight, but it still bears a certain amount of pressure especially when the cluster reaches a certain scale. So I want to optimize the nameserver in RocketMQ 5.0. 2. Provide any additional detail on your proposed use case for this feature. I want to optimize the nameserver from the following aspects (1)By separating the broker registration thread pool and the topic route info acquisition thread pool, we can ensure that different types of requests will not affect each other. (2)Optimize topic routing cache to speed up topic routing acquisition, reduce nameserver CPU pressure. (3) Unregister brokers in batches to speed up the broker offline. Refer to [wiki page](https://github.com/apache/rocketmq/wiki/RIP-29-Optimize-RocketMQ-NameServer) 2. Indicate the importance of this issue to you (blocker, must-have, should-have, nice-to-have). Are you currently using any workarounds to address this issue? nice-to-have 4. If there are some sub-tasks using -[] for each subtask and create a corresponding issue to map to the sub task: - [sub-task1-issue-number](example_sub_issue1_link_here): sub-task1 description here, - [sub-task2-issue-number](example_sub_issue2_link_here): sub-task2 description here, - ... -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
