michaeljmarshall commented on issue #331: URL: https://github.com/apache/pulsar-helm-chart/issues/331#issuecomment-1295358164
I confirmed today that the shutdown is not forceful/ungraceful. It looks like the helm chart does not do any kind of ordering when upgrading components. When a single broker and zookeeper are deployed, that means there will be downtime. In the event that multiple zookeepers are deployed, the rollout strategy will be used and it is less likely we'd see these errors. Closing this issue since helm does not provide a way to do ordered upgrades to components. The main solution for a user is likely to update one component at a time with multiple `helm upgrade` commands. -- 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]
