You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@pulsar.apache.org by GitBox <gi...@apache.org> on 2022/06/03 10:18:10 UTC

[GitHub] [pulsar] Jason918 commented on issue #15225: I want pulsar-discovery to come back.

Jason918 commented on issue #15225:
URL: https://github.com/apache/pulsar/issues/15225#issuecomment-1145817079

   > Would you be able to share more details of what is "proper tuning" for broker clusters for this use case? 
   
   The tuning work mostly includes two aspects, one is broker configuration, like turn-off topic level metrics. The other is solving some OOM issues in bookie(some minor code optimization).
   
   > What are your hardware requirements? 
   Broker use 16C32G, and bookie use 16C48G. One cluster contains 10 brokers and 5 bookies and can host 1.5 million topics. Number of clusters can scale out with pulsar-discovery. 
   
   > How is pulsar-discovery configured and used? 
   Actually we did some optimization on this, like caching all topic route info locally.
   
   > This topic would also be a great talk for [Pulsar Summit](https://pulsar-summit.org/)!
   
   I am working on sharing more details on this topic. Hopefully, it can be done in next few months.


-- 
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-unsubscribe@pulsar.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org