lhotari commented on issue #11687: URL: https://github.com/apache/pulsar/issues/11687#issuecomment-905242842
> As far as I know there is no helm charts for 2.7.3 it stops at 2.7.2 right now or maybe I'm not looking where I should be : > https://github.com/apache/pulsar-helm-chart/tags Yes that's a gap. The reason for that the intention has been to upgrade to Pulsar 2.8.0, but that has some breaking changes and it has been postponed. Pulsar 2.7.3 just hasn't been updated to the Helm chart in the mean time, although it would make sense. It's possible to use the 2.7.2 Helm chart and define the images to use 2.7.3 . One way is to specify the tags in your custom values.yaml: ``` images: zookeeper: tag: 2.7.3 bookie: tag: 2.7.3 autorecovery: tag: 2.7.3 broker: tag: 2.7.3 proxy: tag: 2.7.3 functions: tag: 2.7.3 pulsar_metadata: image: tag: 2.7.3 ``` > Regarding the JVM point, I totally agree, it's just that the memory consumption looks enormous, almost 16Go used in one pod. That's probably an issue. Please retest with Pulsar 2.7.3 to see if it can be reproduced. > I guess the only choice would be to setup memory limits inside the statefull YAML. What do you mean with "stateful YAML"? Your values.yaml passed to helm install/upgrade with `--values`/`-f` ? Yes, it's necessary to tune a lot of Pulsar parameters for production usage. The gap is that the documentation doesn't include detailed instructions about doing so. -- 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]
