[GitHub] [pulsar-helm-chart] hangc0276 commented on pull request #165: useV2WireProtocol for bookkeeper autorecovery

hangc0276 commented on pull request #165: URL: https://github.com/apache/pulsar-helm-chart/pull/165#issuecomment-941868430 > Just for my information can someone explain why Autorecovery should use the V2 protocol but the Broker V3? Thanks in advance! @frankjkelly I broker side, it

[GitHub] [pulsar-helm-chart] frankjkelly commented on pull request #165: useV2WireProtocol for bookkeeper autorecovery

frankjkelly commented on pull request #165: URL: https://github.com/apache/pulsar-helm-chart/pull/165#issuecomment-941069144 Thanks @eolivelli ! -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to

[GitHub] [pulsar-helm-chart] eolivelli commented on pull request #165: useV2WireProtocol for bookkeeper autorecovery

eolivelli commented on pull request #165: URL: https://github.com/apache/pulsar-helm-chart/pull/165#issuecomment-941064004 if you want to leverage ExplicitLAC feature you need V3, so it is better to use V3 on the broker. AutoRecovery needs only to read/write to the bookies, no need

[GitHub] [pulsar-helm-chart] frankjkelly commented on issue #164: 2.7.3 helm chart still use 2.7.2 images

frankjkelly commented on issue #164: URL: https://github.com/apache/pulsar-helm-chart/issues/164#issuecomment-941032822 This was due to my change where I rev'd the Chart version https://github.com/apache/pulsar-helm-chart/commit/5b10f48f5b271a15c000239042c507c33da16fe9 (unfortunately

[GitHub] [pulsar-helm-chart] frankjkelly closed pull request #159: Fix #152 Helm chart does not support Istio port naming

frankjkelly closed pull request #159: URL: https://github.com/apache/pulsar-helm-chart/pull/159 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail:

[GitHub] [pulsar-helm-chart] frankjkelly commented on pull request #165: useV2WireProtocol for bookkeeper autorecovery

frankjkelly commented on pull request #165: URL: https://github.com/apache/pulsar-helm-chart/pull/165#issuecomment-940988386 Just for my information can someone explain why Autorecovery should use the V2 protocol but the Broker V3? Thanks in advance! -- This is an automated message

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

+1 (binding) * check the license headers * install the npm package * build the source and run producer/consumer * verify checksum and signatures Thanks, Nozomi 2021年10月12日(火) 19:26 Masahiro Sakamoto : > This is the first release candidate for Apache Pulsar Node.js client, > version 1.4.1. > >

[VOTE] Pulsar Node.js Client Release 1.4.1 Candidate 1

This is the first release candidate for Apache Pulsar Node.js client, version 1.4.1. The artifacts are exactly the same as the first vote, but I didn't upload them and the signature to the staging repository of dist, so I'll run the vote again. It fixes the following issues:

[GitHub] [pulsar-manager] pgandhap opened a new issue #425: Install Pulsar-manager on kubernetes cluster

pgandhap opened a new issue #425: URL: https://github.com/apache/pulsar-manager/issues/425 Iam wanna to use pulsar-manager for GUI management, monitoring tool and following this https://pulsar.apache.org/docs/en/administration-pulsar-manager/. In this on step ( Set administrator account

RE: [VOTE] Pulsar Node.js Client Release 1.3.2 Candidate 1

Thank you Enrico. I will upload the tarball and other files to dist and then run the vote again. Regards, Masahiro Sakamoto Yahoo Japan Corp. E-mail: massa...@yahoo-corp.jp -Original Message- From: Enrico Olivelli Sent: Tuesday, October 12, 2021 3:50 PM To: Dev Subject: Re: [VOTE]

[CANCELLED] [VOTE] Pulsar Node.js Client Release 1.4.1 Candidate 1

Hi Dave, Thank you for pointing it out. I had a lack of understanding of the release policy, sorry. I'm going to cancel this vote. Regards, Masahiro Sakamoto Yahoo Japan Corp. E-mail: massa...@yahoo-corp.jp -Original Message- From: Dave Fisher Sent: Tuesday, October 12, 2021 3:28 PM

[CANCELLED] [VOTE] Pulsar Node.js Client Release 1.3.2 Candidate 1

Hi Dave, Thank you for pointing it out. I had a lack of understanding of the release policy, sorry. I'm going to cancel this vote. Regards, Masahiro Sakamoto Yahoo Japan Corp. E-mail: massa...@yahoo-corp.jp -Original Message- From: Dave Fisher Sent: Tuesday, October 12, 2021 3:27 PM

[GitHub] [pulsar-dotpulsar] blankensteiner merged pull request #90: Change default behaviour on MetaDataException

blankensteiner merged pull request #90: URL: https://github.com/apache/pulsar-dotpulsar/pull/90 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail:

[GitHub] [pulsar-dotpulsar] kandersen82 opened a new pull request #90: Change default behaviour on MetaDataException

kandersen82 opened a new pull request #90: URL: https://github.com/apache/pulsar-dotpulsar/pull/90 Error occurs when tenant or namespace supplied in topic string does not exist. org.apache.pulsar.broker.web.RestException: Policies not found for tenant/namespace namespace -- This is

Release 2.9.0....adding more PRs ? please don't

Hello, I see that someone is adding PRs to Milestone 30 (Pulsar 2.9.0) we are pretty late on starting the release https://github.com/apache/pulsar/milestone/30 If you have a PR that you really want to see in 2.9.0 please look after it and ensure that it has: - CI passing - no "Request changes"

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

Masahiro, I suggest to create a .tar.gz file with the contents of the release, only source files and copy it to the staging repository https://dist.apache.org/repos/dist/dev/pulsar/ No need to add commits to the repo I believe that if you do this we can continue on the VOTE We should also

[GitHub] [pulsar-manager] thomaeschen commented on issue #310: Support for TLS Authentication & Authorization

thomaeschen commented on issue #310: URL: https://github.com/apache/pulsar-manager/issues/310#issuecomment-940715084 > > What are the possible values for the 1st two parameters. > > @jaschnell the first two values will be the same values you used for configuring a

[GitHub] [pulsar-manager] thomaeschen commented on issue #310: Support for TLS Authentication & Authorization

thomaeschen commented on issue #310: URL: https://github.com/apache/pulsar-manager/issues/310#issuecomment-940713839 Yes, we are currently facing the same issue. Is there any work around way to skip it ? -- This is an automated message from the Apache Git Service. To respond to the

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

> On Oct 8, 2021, at 3:20 AM, Masahiro Sakamoto wrote: > > This is the first release candidate for Apache Pulsar Node.js client, version > 1.3.2. > > It fixes the following issues: > https://github.com/apache/pulsar-client-node/milestone/9?closed=1 > > *** Please download, test and vote on

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

You need at least 3 +1 (binding) votes for this release vote to succeed. Sent from my iPhone > On Oct 11, 2021, at 10:22 PM, Masahiro Sakamoto > wrote: > > Closing the vote with 3 +1 and no -1. > > 2 +1 bindings are: > * Yuto > * Nozomi > 1 +1 non-binding is: > * Guangning > > Masahiro

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

At least 3 +1 (binding) votes are required. I suggest that you hold this open until you get the 3rd vote otherwise this vote fails. Regards, Dave Sent from my iPhone > On Oct 11, 2021, at 10:19 PM, Masahiro Sakamoto > wrote: > > Closing the vote with 2 +1 and no -1. > > 2 +1 bindings are: