sdwerwed edited a comment on pull request #127: URL: https://github.com/apache/pulsar-helm-chart/pull/127#issuecomment-1074108404
@sijie > I think the zone affinity would work for stateless components. I don't think it will work well for stateful components. Because the location of bookie and zookeeper pods will be bound to the location of EBS volumes. This is a known limitation of AWS and probably Azure too, however, the default value is not multi az, if an enginner would like to make it multi az can do it manually with additional steps, not sure if we can handle that in the helm chart anyway, we could document that or if you have another idea how we could make it fully functional with helm let me know. > But you don't configure the rack information, so bookkeeper can potentially place two same copies in the pods running in the same zone. I think I miss some context here as I did not get what is the issue, what do you mean to configure rack information? Do you mean that there is the possibility that data will not be 100% highly available? Feel free to add some more details... -- 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: dev-unsubscr...@pulsar.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
