Re: [DISCUSS] PIP-350: Allow to disable the managedLedgerOffloadDeletionLagInMillis

+1 Best, Ran Gao On 2024/05/10 03:31:13 Yong Zhang wrote: > Hi all, > > I pushed a new proposal to allow to use -1 to disable > the managedLedgerOffloadDeletionLagInMillis to not delete the data from > bookkeeper. > > Please take a look and share your thoughts. Th

Re: [DISCUSS] Upgrading to Jetty 12 since Jetty 9.4.x has reached end-of-line in June 2022

3.3.x +1 The branch-3.2 is the latest branch, and the latest version is 3.2.2, it contains functionality improvements, bug fixes, and CVE fixes, if we happen to release a new version based on branch-3.3, why not add this change to it? Best - Ran Gao On 2024/04/17 17:30:27 Lari Hotari wrote

[ANNOUNCE] Apache Pulsar 3.1.3 released

The Apache Pulsar team is proud to announce Apache Pulsar version 3.1.3. Pulsar is a highly scalable, low latency messaging platform running on commodity hardware. It provides simple pub-sub semantics over topics, guaranteed at-least-once delivery of messages, automatic cursor management for

Re: [VOTE] Pulsar Release 3.1.3 Candidate 2

Close this vote with 3 bindings, thanks for voting. Regards, gaoran10 On 2024/03/07 18:00:26 Ran Gao wrote: > This is the second release candidate for Apache Pulsar version 3.1.3. > > It fixes the following issues: > https://github.com/apache/pulsar/pulls?q=is%3Apr+is%3Amerged+lab

Re: [DISCUSS] Retire pulsar-all Docker image and spin-off Python Functions runtime

+1 Most users don't need all built-in connectors, it's too bloated. Best Regards, Ran Gao On 2024/03/05 23:02:37 Matteo Merli wrote: > The docker image `pulsar-all` is a convenience image that is created on top > of the base `pulsar` image, including all the Pulsar IO connectors a

[VOTE] Pulsar Release 3.1.3 Candidate 2

-091214bca4985694a2e95d6e8432d3790c64e83af1ef0e4f2423833e66073685?context=repo Please download the source package, and follow the README to build and run the Pulsar standalone service. Regards Ran Gao (gaoran10)

Re: [VOTE] Pulsar Release 3.2.1 Candidate 1

+1(non-binding) 1. verify the GPG signature for the below files - apache-pulsar-3.2.1-bin.tar.gz.asc - apache-pulsar-3.2.1-src.tar.gz.asc 2. build the source code 3. test following the release verifying doc. Regards, Ran Gao On 2024/03/05 07:05:05 guo jiwei wrote: > This is the first rele

[VOTE] Pulsar Release 3.1.3 Candidate 1

-219cf93ea289254de127bb52e0c0f1d324a6891fda583ec2ade02c0b0b5a508f?context=repo Please download the source package, and follow the README to build and run the Pulsar standalone service. Regards Ran Gao (gaoran10)

Re: [ANNOUNCE] New Committer: Asaf Mesika

Congratulations, Asaf! Best Regards, Ran Gao On 2024/02/20 16:50:29 Lari Hotari wrote: > The Apache Pulsar Project Management Committee (PMC) has invited > Asaf Mesika https://github.com/asafm to become a committer and we > are pleased to announce that he has accepted. >

Re: [DISCUSS] Migrate CLI parser from jcommander to picocli

+1 (non-binding), it's more elegant. There will be a lot of changes, we can create some tasks based on commands. - Ran Gao On 2024/02/21 05:07:46 Zixuan Liu wrote: > Hi Pulsar Community, > > The pulsar CLI(pulsar-admin, pulsar-client, pulsar-shell, and so on) uses > the jcommande

Re: [VOTE] PIP-280 : Refactor CLI Argument Parsing Logic for Measurement Units using JCommander's custom converter

+1 (non-binding) Thanks, Ran Gao On 2023/07/07 09:25:22 Joo Hyuk Kim wrote: > Hi community, > > This PIP has received a couple of approvals in github PR link [1] > So I thought it's time to vote. > > ## Motivation > > In the current Pulsar codebase, the logi

Re: [VOTE] PIP-239: Retry Mechanism per Message title

+1 (non-binding) Thanks, Ran Gao On 2023/01/08 15:05:31 Zixuan Liu wrote: > +1 (non-binding) > > Thanks, > Zixuan > > Yunze Xu 于2023年1月8日周日 22:38写道： > > > +1 (binding) > > > > Thanks, > > Yunze > > > > On Sun, Jan 8, 2023

Re: [DISCUSS] Introduce oshi library to sensory OS resources

+1 Thanks, Ran Gao On 2022/12/21 09:38:01 Zike Yang wrote: > +1 > > Thanks, > Zike Yang > > On Wed, Dec 21, 2022 at 5:06 PM Yunze Xu wrote: > > > > +1 > > > > Thanks, > > Yunze > > > > On Wed, Dec 21, 2022 at 5:02 PM houxiaoyu wrot

Re: [VOTE] Pulsar Node.js Client Release 1.8.0 Candidate 2

+1 (non-binding) - Checked npm package https://www.npmjs.com/package/pulsar-client/v/1.8.0-rc.2 - Checked source code + napi-darwin-unknown-arm64 work on macOS 12.6 (M1 Pro chip) Thanks, Ran Gao On 2022/12/27 08:29:35 Zike Yang wrote: > Hi everyone, > > This is the second release

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

Re: [VOTE] PIP-222: Add CommandPartitionedTopicMetadata metrics

+1 (unbinding) Thanks, Ran On 2022/11/17 09:06:50 Jiuming Tao wrote: > Dear Pulsar Community, > > Please review and vote on this PIP. > > PIP link: https://github.com/apache/pulsar/issues/18319 > > > Discuss thread: >

Re: [VOTE] PIP-195: New bucket based delayed message tracker

+1 Great work! Thanks, Ran Gao On 2022/08/29 10:37:31 Cong Zhao wrote: > Hi Pulsar Community, > > In order to facilitate community review, I copied this proposal to Google > Docs, please review it and complete the vote. > > PIP: > https://docs.

Re: Required and recommended JavaVersion for Pulsar broker

One problem is that the presto 334 needs jdk11+ and it didn't support jdk8, maybe 2.11 is a good time for Pulsar to upgrade the Presto to 334+ or the latest stable version. On 2022/06/22 18:22:09 Enrico Olivelli wrote: > For Pulsar 2.9 and 2.10 you should use jdk11 > you can checkout the

Re: Pulsar Documentation Guides

Great work! On 2022/06/13 16:00:00 Yu wrote: > Hi team, > > This is a soft reminder: > > If you make contributions to Pulsar documentation, please follow these > guides to improve your PR quality and get your PR merged quickly. > > - Pulsar Documentation Writing Style Guide [1] > - Pulsar

Re: [VOTE] Pulsar Release 2.10.1 Candidate 1

+1 (non-binding) Verification list: 1. Build source code. (MacOS 12.2.1, Chip Apple M1 Pro) 2. Start standalone. 3. Producing and consuming tests based on perf tool. 4. Query bytes data by Pulsar SQL. 5. Using the binary package execute same operations. On 2022/06/13 11:42:59 PengHui Li wrote: >

Re: [DISCUSS] [PIP-165] Auto release client useless connections

nection. If we do not optimize the broker > load balancing algorithm, all connections are considered useful connections. > When the cluster is large, holds so many connections becomes redundant. > Later, I will try to put forward other proposals to improve this > phenomenon, s

Re: [DISCUSS] [PIP-165] Auto release client useless connections

This is a good idea, but I have a concern, Pulsar has the config `brokerMaxConnections` to control max connection count against one broker. If the connection is closed, it will re-connect when consumers or producers start to consume and produce messages again, but this time the max connection

Re: [VOTE] [PIP-158] Split client TLS transport encryption from authentication

+1 (non-binding) Best, Ran On 2022/05/10 08:46:26 Zixuan Liu wrote: > Hi Pulsar community, > > Voting for https://github.com/apache/pulsar/issues/15289 > > Discussion thread: > https://lists.apache.org/thread/fblmm8oc7h907cfnppvk71o2cbp5mk8q > > Thanks, > Zixuan > > -- > > ## Motivation

Re: [VOTE] [PIP-153] Optimize metadataPositions in MLPendingAckStore

+1 (non-binding) Best, Ran On 2022/04/25 06:54:58 一苇以航 wrote: > Hi Pulsar Community. > > This is the voting thread for PIP-153. It will stay open for at least 48 > hours. > > The proposal can be found:https://github.com/apache/pulsar/issues/15073 > > Discuss thread: >

Re: [DISCUSSION] PIP-156: Enable system topic by default

+1 (non-binding) Best, Ran On 2022/04/26 12:07:32 guo jiwei wrote: > Hi community: >In PIP-39 > , > we have introduced namespace event to support topic level policy. This > feature was released in Pulsar 2.6. > >

Re: [ANNOUNCE] new Committer Qiang Zhao (mattisonchao)

Congratulations! Qiang best, Ran On 2022/05/04 06:28:24 Enrico Olivelli wrote: > The Project Management Committee (PMC) for Apache Pulsar > has invited Qiang Zhao to become a committer and we are pleased > to announce that he has accepted. > > Qiang Zhao (with GH id mattisonchao) contributed

Re: Call for projects and mentors for OSPP 2022

: Prepare a design for this feature. Item 3: Start coding. Item 4: Add unit and integration tests. Item 5: Add doc for this feature. Project Mentor: Your Name: Ran Gao Your Email: r...@apache.org Your Apache ID: rgao On 2022/04/24 13:23:18 PengHui Li wrote: > Hi all, > > Open Source

Re: [VOTE] [PIP-154] Max active transaction limitation for transaction coordinator

I think this is a valuable improvement, it could make the Pulsar transaction more stable, great work. +1 best, Ran Gao On 2022/04/24 02:00:39 丛搏 wrote: > Hi Pulsar community, > > This is the voting thread for PIP-154. It will stay open for at least 48 > hours. > > The pro

[ANNOUNCE] Apache Pulsar 2.9.2 released

The Apache Pulsar team is proud to announce Apache Pulsar version 2.9.2. Pulsar is a highly scalable, low latency messaging platform running on commodity hardware. It provides simple pub-sub semantics over topics, guaranteed at-least-once delivery of messages, it also provides transaction feature

Re: [DISCUSS] [PIP-154] Max active transaction limitation for transaction coordinator

Bo, Great work! +1 best, Ran Gao On 2022/04/12 12:44:36 丛搏 wrote: > pipHi Pulsar community, > > I open a pip to discuss Max active transaction limitation for > transaction coordinator. > link: https://github.com/apache/pulsar/issues/15133 > > > Thanks, > Bo >

Re: [ANNOUNCE] New Committer: Zhangmin Gao

+1 Best, Ran Gao On 2022/04/13 09:35:57 PengHui Li wrote: > The Apache Pulsar Project Management Committee (PMC) has invited Zhangmin > Gao > https://github.com/gaozhangmin to become a committer and we are pleased to > announce that he has accepted. > > Welcome and Congratulat

Re: [VOTE] PIP-149: Making the REST Admin API fully async

+1 Ran Gao On 2022/03/25 02:13:26 mattison chao wrote: > This is the voting thread for PIP-149. It will stay open for at least 48 > hours. > > https://github.com/apache/pulsar/issues/14365 > > Pasted below for quoting convenience. > > - > > Motivation &g

Re: [DISCUSS] PIP-155: Drop support for Python2

+1 Ran Gao Best On 2022/04/15 16:06:36 Matteo Merli wrote: > https://github.com/apache/pulsar/issues/15185 > > - > > ## Motivation > > Python 2.x has been deprecated for many years now and it was > officially end-of-lifed 2.5 years ago > (https://www.pyt

Re: [ANNOUNCE] New Committer: Ruguo Yu

Congratulations! Ran Best On 2022/04/15 10:06:44 Yu wrote: > The Apache Pulsar Project Management Committee (PMC) has invited Ruguo Yu ( > https://github.com/yuruguo) to become a committer and we are pleased to > announce that he has accepted. > > Welcome and Congratulations, Ruguo Yu! > >

Re: [ANNOUNCE] New Committer: Zike Yang

Hi, zike, congratulations! Ran Gao Best On 2022/04/13 09:34:23 PengHui Li wrote: > The Apache Pulsar Project Management Committee (PMC) has invited Zike Yang > https://github.com/RobertIndie to become a committer and we are pleased to > announce that he has accepted. >

Re: [VOTE] Pulsar Release 2.9.2 Candidate 4

Thanks for voting, there are 3 bindings, I'll create the final tag `2.9.2` and finish the subsequent release process. On 2022/03/23 04:31:17 Hang Chen wrote: > +1 (binding) > > - Checked checksum and license > - Setup standalone cluster and run pulsar perf to produce and consume > - Check the

[VOTE] Pulsar Release 2.9.2 Candidate 4

This is the fourth release candidate for Apache Pulsar, version 2.9.2. *** Please download, test, and vote on this release. This vote will stay open for at least 72 hours *** Note that we are voting upon the source (tag), binaries are provided for convenience. Source and binary files:

Re: [VOTE] Pulsar Release 2.9.2 Candidate 3

And I suggest to do this with PIP in the next major version release. > > For version 2.9.2, we need merge 14409 to avoid return null value. > > > > > > > > Wangjialing > > > > From: Ran Gao > > Date: 2022-02-17 02:26 > > To: dev > > Subje

Re: [VOTE] Pulsar Release 2.8.3 Candidate 2

+1 - Check src build - Check run standalone mode by binary package - Check Basic publish and consume partitioned topic - Check Pulsar SQL query bytes data On 2022/02/16 04:34:55 Michael Marshall wrote: > This is the second release candidate for Apache Pulsar, version 2.8.3. > > It fixes the

[VOTE] Pulsar Release 2.9.2 Candidate 3

This is the third release candidate for Apache Pulsar, version 2.9.2. *** Please download, test, and vote on this release. This vote will stay open for at least 72 hours *** Note that we are voting upon the source (tag), binaries are provided for convenience. Source and binary files:

Re: [VOTE] Pulsar Release 2.9.2 Candidate 2

Yes, all necessary PRs are cherry-picked to branch-2.9, and the test pass, refer to https://github.com/apache/pulsar/commits/branch-2.9, I'm cutting the new RC from the current branch-2.9. On 2022/02/15 14:57:25 Enrico Olivelli wrote: > Ran, > Are we cutting the new RC from the current

[VOTE] Pulsar Release 2.9.2 Candidate 2

Sorry, the 2.9.2 release candidate-1 has a wrong sign certificate. This is the second release candidate for Apache Pulsar, version 2.9.2. *** Please download, test, and vote on this release. This vote will stay open for at least 72 hours *** Note that we are voting upon the source (tag),

Re: [VOTE] Pulsar Release 2.9.2 Candidate 1

aded one. > > Regards, > Penghui > > On Sun, Jan 23, 2022 at 9:25 PM Ran Gao wrote: > > > This is the first release candidate for Apache Pulsar, version 2.9.2. > > > > It fixes the many issues and the log4j security problem. > > > > *** Please downlo

Re: [DISCUSS] Apache Pulsar 2.9.2 release

; > > I hope we will review carefully what we are including in the release > > > > And that we will let branch-2.9 stabilise by not adding any other commits > > that are not strictly required: > > - security related issues > > - data loss/data corruption cases > &

Re: [DISCUSS] Apache Pulsar 2.9.2 release

e release > > And that we will let branch-2.9 stabilise by not adding any other commits > that are not strictly required: > - security related issues > - data loss/data corruption cases > > > Enrico > > > Thank you Ran Gao for starting this thread. > > > > En

[VOTE] Pulsar Release 2.9.2 Candidate 1

This is the first release candidate for Apache Pulsar, version 2.9.2. It fixes the many issues and the log4j security problem. *** Please download, test, and vote on this release. This vote will stay open for at least 72 hours *** Note that we are voting upon the source (tag), binaries are

[DISCUSS] Apache Pulsar 2.9.2 release

PRs are labeled release/2.9.2 but not cherry-pick to branch-2.9, I'll cherry-pick them, and there are also 20 open PRs are labeled release/2.9.2, I'll follow them to make sure important fix could be merged in 2.9.2. Best, Ran Gao [0] https://github.com/apache/pulsar/compare/v2.9.1...branch-2.9

Re: [VOTE] PIP-130: Apply redelivery backoff policy for ack timeout

+1 Best, Ran Gao On 2022/01/04 03:34:33 PengHui Li wrote: > This is the voting thread for PIP-130. It will stay open for at least 48 > hours. > > https://github.com/apache/pulsar/issues/13528 > > Pasted below for quoting convenience. > > - > > PIP 130: A

Re: [VOTE] Apache Pulsar 2.9.0 candidate 4

Hi Enrico, Thanks for your great work! We also make some chaos tests for 2.9.0 candidate 4. We opened a new Pulsar cluster based on 2.9.0-candidate-4 and injected some chaos experiments by chaos-mesh, such as broker pod failure, kill, and zookeeper pod failure, in this process, the entire

Re: [ANNOUNCE] New Committer: Jiwei Guo

Congrats Jiwei! Ran On 2021/11/22 04:35:08 PengHui Li wrote: > The Apache Pulsar Project Management Committee (PMC) has invited Jiwei Guo > https://github.com/Technoboy- to become a committer and we are pleased to > announce > that he has accepted. > > Jiwei has joined the community for more

Re: Virtual Pulsar Community Meetings

+1 @sijie The virtual Pulsar community meeting is so cool and I think Sijie's proposal is more reasonable, thanks. Best Regards, Ran On 2021/01/29 08:53:40, Sijie Guo wrote: > That's a super great idea! Thank you for bringing this up! > > Given there are a lot of committers/contributors are