[NOTICE] Enter code freeze phase of Pulsar 3.0.0 release

2023-04-11 Thread Zike Yang
Hi, all We would like to inform you that the Pulsar 3.0.0 release has entered the code freeze phase, with the branch-3.0 cut and RC1 currently being built. As per our release policy [0]. from the code-freeze point, to minimize the risk of delaying the release, only bug fixes involving a regressio

Re: [DISCUSS] PIP-255: Assign topic partitions to bundle by round robin

2023-04-11 Thread Lin Lin
As I mentioned in the implementation of PIP, we will plug-in the partition assignment strategy. However, in the same cluster, it is impossible for some Brokers to use consistent hashing and some Brokers to use round robin. On 2023/04/11 07:37:19 Xiangying Meng wrote: > Hi Linlin, > > This is a

Re: Call for projects and mentors for OSPP 2023

2023-04-11 Thread Xiangying Meng
## Project Info Project Name: Pulsar Transaction Isolation Level Enhancement Project Description: Implement configurable isolation levels for Pulsar transactions to enhance flexibility. The project will introduce Read Committed and Read Uncommitted isolation levels and allow consumers to configure

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

2023-04-11 Thread Baodi Shi
Hi, tison. Thanks for your feedback. I noticed that the master branch also doesn't have NOTICE files. I'll add it first and then launch release 1.8.2-rc.3 Thanks, Baodi Shi On Apr 12, 2023 at 10:14:20, tison wrote: > Thank you! I can successfully run the example. > > However, -1 because the s

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

2023-04-11 Thread tison
Thank you! I can successfully run the example. However, -1 because the source release doesn't contain a NOTICE file. Other check items including LICENSE, license headers, checksum and GPG sign should be fine. Best, tison. Baodi Shi 于2023年4月12日周三 09:48写道: > This example connects test env. May

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

2023-04-11 Thread Baodi Shi
This example connects test env. Maybe it's network latency or server instability. You can try again. BTW: The token expires in tls-token.js . I updated it, you can pull the main branch and try it. Thanks, Baodi Shi On Apr 12, 2023 at 00:22:53, Zili Chen wrote: > Hi Baodi, > > When running t

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

2023-04-11 Thread Zili Chen
Hi Baodi, When running the tls test you provided, I encountered this error: $ node tls-oauth2.js [INFO][ClientConnection:190] [ -> pulsar+ssl://baodi-test-7407d844-b456-49e1-987c-24f1a5c162cb.usce1-whale.test.g.sn2.dev:6651] Create ClientConnection, timeout=1 [INFO][ConnectionPool:97] Crea

[DISCUSS] File missing on distro and hotfix

2023-04-11 Thread tison
Hi, I noticed an issue that the 2.11.0 distro misses a config file for examples[1]. Since we're closing to the 3.0.0 release process, I'd like to bring this topic here for: 1. As a reminder for 3.0.0 RMs to check the existence of these files after making the distro. 2. Discuss if we can re-upload

Re: [VOTE] Pulsar Node.js Client Release 1.8.2 Candidate 1

2023-04-11 Thread Baodi Shi
Hi, all The 1.8.2-rc.2 has been released. Please help verify it. It contains the following two PRs: - https://github.com/apache/pulsar-client-node/pull/316 - https://github.com/apache/pulsar-client-node/pull/309 https://lists.apache.org/thread/72240tgq5bct78rdslzc689w6h9nb8z0 Thanks, B

[VOTE] Pulsar Node.js Client Release 1.8.2 Candidate 2

2023-04-11 Thread Baodi Shi
Hi everyone, This is the first release candidate for Apache Pulsar Node.js client, version 1.8.2. It fixes the following issues: https://github.com/apache/pulsar-client-node/pulls?q=is%3Apr+label%3Arelease%2Fv1.8.2+is%3Aclosed Please download the source files and review this release candidate: -

Re: Call for projects and mentors for OSPP 2023

2023-04-11 Thread Xiangying Meng
Hi Dianjin, Thank you for sharing the exciting news about Apache Pulsar's participation in OSPP 2023. I would also like to express my interest in joining this year's event as a mentor for the Pulsar project. We are planning to work on implementing isolation levels for Pulsar. I will send you the

Re: [VOTE] Pulsar Node.js Client Release 1.8.2 Candidate 1

2023-04-11 Thread Zike Yang
Hi, all I have created a PR https://github.com/apache/pulsar-client-node/pull/316 for that issue. PTAL and help review. Thanks, Zike Yang On Tue, Apr 11, 2023 at 5:57 PM Baodi Shi wrote: > > Hi, @Nozomi Kurihara > > Ok, We can wait for this issue fixed > https://github.com/apache/pulsar-client

Re: [VOTE] Pulsar Node.js Client Release 1.8.2 Candidate 1

2023-04-11 Thread Baodi Shi
Hi, @Nozomi Kurihara Ok, We can wait for this issue fixed https://github.com/apache/pulsar-client-node/issues/315. Thanks, Baodi Shi On Apr 11, 2023 at 17:54:56, Nozomi Kurihara wrote: > Hi Baodi, Zike, > > Thank you for clarifying the issue status. > Although this is not a regression bug,

Re: [VOTE] Pulsar Node.js Client Release 1.8.2 Candidate 1

2023-04-11 Thread Nozomi Kurihara
Hi Baodi, Zike, Thank you for clarifying the issue status. Although this is not a regression bug, I prefer including the fix to the current 1.8.2 release since it is easily reproducible and causes unlimited memory usage increase. Thanks, Nozomi 2023年4月11日(火) 18:01 Zike Yang : > Hi, > > https://

Re: Call for projects and mentors for OSPP 2023

2023-04-11 Thread Yu
Thanks Dianjing! This is an activity worth attending based on my previous experience. As a mentor for OSPP 2021 and 2022, I collaborated with some students and @urfreespace to create fresh content experiences for Pulsar, such as Introducing a Bot to Improve the Efficiency of Developing Docs [1] an

Re: [VOTE] Pulsar Node.js Client Release 1.8.2 Candidate 1

2023-04-11 Thread Zike Yang
Hi, https://github.com/apache/pulsar-client-node/issues/308 is not a regression bug. I don't think we need to block this RC. > May you share the link to the issue? There seems no such reference in PR-309. I have created an issue to track it: https://github.com/apache/pulsar-client-node/issues/31

Re: [VOTE] Pulsar Node.js Client Release 1.8.2 Candidate 1

2023-04-11 Thread tison
Hi Baodi, > there is one Reader related issue May you share the link to the issue? There seems no such reference in PR-309. Best, tison. Baodi Shi 于2023年4月11日周二 16:17写道: > Hi, > I noticed that there is one Reader related issue for this that needs to be > fixed, so I guess it could be include

Re: [VOTE] Pulsar Node.js Client Release 1.8.2 Candidate 1

2023-04-11 Thread Baodi Shi
Hi, I noticed that there is one Reader related issue for this that needs to be fixed, so I guess it could be included in 1.8.3. Thanks Baodi Shi On Tue, Apr 11, 2023 at 15:39 Nozomi Kurihara wrote: > Hi Baodi, > > Thank you for starting the release process. > > I think https://github.com/apache

Re: [VOTE] Pulsar Node.js Client Release 1.8.2 Candidate 1

2023-04-11 Thread Nozomi Kurihara
Hi Baodi, Thank you for starting the release process. I think https://github.com/apache/pulsar-client-node/pull/309 seems an important fix. Should we include it in the 1.8.2 release or postpone it to the next release? Thanks, Nozomi

Re: [DISCUSS] PIP-255: Assign topic partitions to bundle by round robin

2023-04-11 Thread Xiangying Meng
Hi Linlin, > This is an incompatible modification, so the entire cluster needs to be upgraded, not just a part of the nodes Appreciate your contribution to the new feature in PIP-255. I have a question regarding the load-balancing aspect of this feature. You mentioned that this is an incompatibl

Re: [DISCUSS] PIP-255: Assign topic partitions to bundle by round robin

2023-04-11 Thread Lin Lin
> Do we expect that the bundles should have the same loads? Yes.If the bundle load is similar, it will be easier to achieve a balanced state during subsequent load balancing. If the bundle loads are different or there are hot bundles, it will trigger bundle split or unload. Unload the hotspot bu

Re: [DISCUSS] PIP-250: Add proxyVersion to CommandConnect

2023-04-11 Thread Xiangying Meng
Hi Michael, I appreciate your detailed explanation. I agree with your proposal. It seems that sharing version information between the proxy and broker would indeed be beneficial for debugging purposes without creating an unnecessary tight coupling between the two components. I appreciate your wi