poorbarcode commented on PR #24423: URL: https://github.com/apache/pulsar/pull/24423#issuecomment-2982738371
> Instead, a more effective solution would be to have a rate limiter or semaphore in place that specifically targets the topic patter listing responses and watchers. When this is handled asynchronously, the solution could add delay to responding to requests when limits are reached. > Besides GET_TOPICS_OF_NAMESPACE/GET_TOPICS_OF_NAMESPACE_RESPONSE, there's also WATCH_TOPIC_LIST with WATCH_TOPIC_LIST_SUCCESS and WATCH_TOPIC_UPDATE responses. That's why it makes more sense to design a proper backpressure fore topic listings. For the scenario that I described [here](https://github.com/apache/pulsar/pull/24423#issuecomment-2982735382), for different namespaces, which have different quantities of topics, we can hardly set an appropriate value for the rate-limiter. So the current implementation is better. -- 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...@pulsar.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
