Re: [VERIFY] Pulsar Release 3.2.0 Candidate 3

2024-01-22 Thread guo jiwei
Hi Lari, I will build the new candidate-4 soon. Regards Jiwei Guo (Tboy) On Mon, Jan 22, 2024 at 5:02 AM Lari Hotari wrote: > Thank you for reviewing and merging the PR #21937 (restoring the broker id > format). I have cherry-picked that to branch-3.2 together with it's > dependency PR #218

Re: [VERIFY] Pulsar Release 3.2.0 Candidate 3

2024-01-21 Thread Lari Hotari
Thank you for reviewing and merging the PR #21937 (restoring the broker id format). I have cherry-picked that to branch-3.2 together with it's dependency PR #21894 (fixes leader broker election when advertised listeners is configured) and in addition #21871 (pulsar-bom). >From my side we are re

Re: [VERIFY] Pulsar Release 3.2.0 Candidate 3

2024-01-20 Thread Lari Hotari
As a follow up, I have created https://github.com/apache/pulsar/pull/21937 to restore the broker id (previously called "lookup service address") to match the format used in existing Pulsar releases. There was a misconception that PR #17136 would have changed the broker id ("lookup service addre

Re: [VERIFY] Pulsar Release 3.2.0 Candidate 3

2024-01-19 Thread Lari Hotari
-1 from my side. Explanation: I didn't notice until now that the "lookup service address" (now brokerId ) was modified for 3.2.0 in this PR https://github.com/apache/pulsar/pull/21015 based on this issue report https://github.com/apache/pulsar/issues/21012 . I'm waiting for answers on the ques

[VERIFY] Pulsar Release 3.2.0 Candidate 3

2024-01-18 Thread guo jiwei
This is the third release candidate for Apache Pulsar version 3.2.0. It fixes the following issues: https://github.com/apache/pulsar/milestone/36?closed=1 *** Please download, test and verify on this release. This release candidate verification will stay open until Jan 25 *** Note that we are ve