eolivelli commented on pull request #96: URL: https://github.com/apache/pulsar-helm-chart/pull/96#issuecomment-770373037
Currently the bookie id generated by the bookie is computed from the main bookie protocol endpoint. In the future we are going to add new endpoints and protocols (as in your SNI patch) Having references to the current port is a burden we should take off. In case of Kubernetes the pod name looks like a good and meaningful id. Another option would be to let the bookie generate an UUID and store it locally on disk, as we are doing in HerdDB. Regarding the upgrade story: this is the hard point and I still haven't found a good solution, this is why this PR is only a draft. It would be good to have the ability to use the BookieID configured only for new bookies for instance. But I don't know if this is feasible with an helm chart. ---------------------------------------------------------------- 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. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
