Re: [VOTE] Pulsar Client Python Release 3.0.0 Candidate 3

I'm closing this vote. 3 binding +1s: * Matteo * Penghui * Jiwei 1 non-binding +1: * Bo Thanks, Yunze On Fri, Dec 23, 2022 at 1:43 PM Dave Fisher wrote: > > I haven’t had a chance to review this RC yet, but I did notice the > reorganization of the directories and wanted to compliment this cha

Re: [VOTE] Pulsar Client Python Release 3.0.0 Candidate 3

Hi, Yunze, I found that there is still `-candidate-3` suffix in the source release files: https://dist.apache.org/repos/dist/release/pulsar/pulsar-client-python-3.0.0/ I think It should not contain the candidate suffix for both candidate files and release files. BR, Zike Yang On Mon, Dec 26, 20

Re: [DISCUSS] Change the default IO threads and listener threads of Java Client

It seems this change will not affect the consumer, because the default executor is a single-thread executor service, increasing the listener threads number will allocate different single-thread executor services to different consumers. On 2022/12/21 09:01:39 Yunze Xu wrote: > I have a concern ab

Re: [DISCUSS] Change the default IO threads and listener threads of Java Client

I am sorry, I am late on this train. Unfortunately if you have to connect using different authentication parameters you need to open many PulsarClients. I think that we can change this default but we should provide an official API to share the threadpools between the clients. There is no need to

Re: [VOTE] Pulsar Client Python Release 3.0.0 Candidate 3

Hi zike, Thanks for your reminder. It's caused by the wrong steps of the release process. I think we can simply rename these files to remove the `-candidate-3` suffix, which requires the PMC's permission to do that. I will ask a PMC to do that. Thanks, Yunze On Mon, Dec 26, 2022 at 7:31 PM Zike

Re: [DISCUSS] Change the default IO threads and listener threads of Java Client

> I think that we can change this default but we should provide an official API to share the threadpools between the clients. That sounds good to me. Since it will introduce a new API to the client side. I will create a new proposal for the API changes. Thanks, Penghui On Mon, Dec 26, 2022 at 8:

Re: [PROPOSAL] Website precommit and move the source of docs to the site repo

FYI tracking issue has been created: https://github.com/apache/pulsar/issues/19064 I plan to finish it by the end of next month. Best, tison. tison 于2022年12月21日周三 11:33写道： > Thanks for your feedback! > > @Yu > > Thanks for sharing the previous thread. I looped in @michaeljmarshall > here. > >

[VOTE] Pulsar Release 2.11.0 Candidate-4

This is the fourth release candidate for Apache Pulsar, version 2.11.0. This release contains 1616 commits by 61 contributors. https://github.com/apache/pulsar/compare/v2.10.2...v2.11.0-candidate-4 CI for this release candidate https://github.com/Technoboy-/pulsar/pull/24 *** Please download, te

Re: [VOTE] Pulsar Release 2.11.0 Candidate-4

+1 (binding) - Checked the signature - Build from source - Checked license - Start standalone with zookeeper - Done some simple performance test( publish, consume, and drain backlog) - Checked function - Checked Cassandra connector - Checked stateful function Thanks, Penghui On Tue, Dec 27, 202

[DISCUSS] Merge two conflicting configuration items about message dispacth throttling

Hi, pulsar community: We introduced dispatch throttling as part of PIP-3 which helps brokers to control fan-out and prevent broker's instability due to large message dispatch. There are two strategies for batch message sending: 1. Enable the conf `preciseDispatcherFlowControl`: Cache the avg num