+1 In the case of a large number of clients, the acquisition of routes will gradually become a bottleneck. I agree with the use of topic caching to reduce the pressure on the nameserver. In the sharing of manyusers, we have seen that many users have used thread pool isolation. , so it's best to push this change upstream for now.
jinrongtong <[email protected]> 于2022年1月14日周五 10:43写道： > Hi, RocketMQ Community: > > 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 start a RIP to > optimize the nameserver in RocketMQ 5.0. > > 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. > > And there will be no compatibility issues in this RIP. > > Refer to the document for more details： > https://shimo.im/docs/pXgKrCwxhCcTwPkx/ > > I can not log in to Google Docs now, so I put the document on shimo and I > will put it on Google Docs later. > > If you have any questions, please reply to this email or comment on the > document. > > > > Thanks > RongtongJin
