Michael Marshall
Michael Marshall
@mattisonchao - yes, that makes sense to me for docker-compose. Ideally, we will also make it configurable in the pulsar helm chart.
I think a release for every change would lead to too many releases. However, there is an underlying problem that this issue points to: contributors to the helm chart feel...
Thanks for your proposal @frankjkelly. Since we are updating the helm chart's release process, as proposed here #301, I am going to close this issue.
> @sdwerwed: 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...
I proposed the following solution in https://github.com/apache/pulsar/pull/8796#issuecomment-802923466. It's copied here: > I think the easiest way to prevent a breaking change in the helm chart is to default to using...
@sijie and @lhotari - what are your thoughts here? It'd be good to solve this soon so that it doesn't affect end users when we release 2.8.0 soon. I see...
In thinking more about this more, we have a problem for our users that upgrade to 2.8.0 from any previous version of pulsar. The persistent data written by prior bookie...
I am going to merge this now, and then I'll test it in https://github.com/apache/pulsar-helm-chart/pull/306
Thank you for your contribution @smazurov!
@thinker0 - which version of Pulsar are you using? This issue references using brokers running 2.8.1. A fix for this issue (or a similar one) was released in 2.8.2 and...