Re: Failover Subscription - consumer assignment logic discussion

Bumping this up. Would really like to discuss this in the community. Regards On Wed, Jun 28, 2023 at 11:49 PM Girish Sharma wrote: > Hi everyone, I am trying to understand the failover subscription logic a > bit more in detail. Specifically, the doc >

Re: [VOTE] PIP-276: Add metric `pulsar_topic_load_times

Close the vote with 4(+1 binding) 2(+1 non-binding) 0(-1) binding: Hang Yunze Mattison Penghui non-binding Yubiao Asaf Regards Jiwei Guo (Tboy) On Mon, Jun 26, 2023 at 10:30 PM Hang Chen wrote: > +1 (binding) > > Thanks, > Hang > > Yunze Xu 于2023年6月26日周一 19:59写道： > > > > +1 (binding)

Re: [DISCUSS] Release Pulsar 3.0.1

Hi Zike, I have cherry-picked 3 PRs intro branch-3.0. All of them of well-understand bugs and performance issues. https://github.com/apache/pulsar/pull/20647 https://github.com/apache/pulsar/pull/20669 https://github.com/apache/pulsar/pull/20607 Thanks, Penghui On Fri, Jun 30, 2023 at 2:48 PM Y

Re: [DISCUSS] Cherry-pick PR-16059 to 2.10 to prevent infinite unloading

> `removeMostServicingBrokersForNamespace ` is introduced by [1] to solve the problem that when all bundles in a particular namespace belong to 1 or few machines, customers owning that namespace will be heavily impacted if that broker goes down. Of course, this PR caused the infinite unloading issu

Re: [DISCUSS] Cherry-pick PR-16059 to 2.10 to prevent infinite unloading

+1 Enrico Il Dom 2 Lug 2023, 06:19 Hang Chen ha scritto: > +1 for cherry-picking it to branch-2.10. We have a flag to control > whether to enable or disable it. > > `removeMostServicingBrokersForNamespace ` is introduced by [1] to > solve the problem that when all bundles in a particular namesp