otmanel31 opened a new issue #12160: URL: https://github.com/apache/pulsar/issues/12160
Hi, To begin, i'm not able to labelize this issue as a question. Could you move the label ? We are in production since almost a year now. Today our Pulsar platform manage 26 000+ topics with 4 brokers, 4 proxies, 3 bookies and 3 zookeeper. The number of connections we have are under our forecast due to customer issue in selling its safe home services. We are in version 2.6.1 and in load balancing and running on Kubernetes server version 1.18.20 (Rancher). We are encountering issues on RAM usage which is increasing regularly on bookies and brokers. We are rebooting one by one bookies and it do not lead to any issues. Conversely for brokers this is not the same story. We rebooted one broker (deleting a pod at Kubernetes-Rancher level which generate automatically the creation of a new pod) 2 months ago and it has remained without any connections despite the load balancing mode over these 2 months. Now we are back to a stable situation where all 4 brokers have a one fourth of the connections. So, what is the procedure on a load balanced Pulsar platform to reboot a single broker without almost no disturbance. More broadly is there any documentation on run operations of a Pulsar platform available. Thanks you for your advice :) -- 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]
