[GitHub] [pulsar-helm-chart] sdwerwed edited a comment on pull request #127: Antiaffinity with zone topology for high availability

sdwerwed edited a comment on pull request #127: URL: https://github.com/apache/pulsar-helm-chart/pull/127#issuecomment-859123386 Hello @sijie, can you have a look at this PR, let me know if any other action is required from my side. -- This is an automated message from the Apache Git Ser

Re: [apache/pulsar] [website] website upgrade (#11766)

This is a question for the dev@pulsar list and not a blocker for infrastructure. I don’t think there is an overriding requirement to preserve docs from incubating releases. If there were then there are other ways to find and regenerate these docs. Regards, Dave Sent from my iPhone > On Dec 19

Re: [DISCUSSION] PIP-120: Enable client memory limit by default

+1 On 12/17/2021 14:43，mattison chao wrote： +1 On Fri, 17 Dec 2021 at 13:56, 陳智弘 wrote: +1 Sijie Guo 於 2021年12月17日 週五 12:38 寫道： +1 On Tue, Dec 14, 2021 at 11:20 AM Matteo Merli wrote: https://github.com/apache/pulsar/issues/13306 Pasted below for quoting convenience. ## Mot

Re: [DISCUSSION] PIP-117: Change Pulsar standalone defaults

My two cents +1 , In my case, i sometimes need to run pulsar standalone in some server with limited resources. > Proposed changes The other point i can think of is maybe schema storage also need to change from using BK to using local filesystem or some else. Best Regards, Lan Liang On

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

+1 (binding) * Checked the license headers * Verified the checksum and signature * Built the source and run producer/consumer Masahiro Sakamoto Yahoo Japan Corp. E-mail: massa...@yahoo-corp.jp -Original Message- From: Nozomi Kurihara Sent: Friday, December 17, 2021 8:25 PM To: dev@puls

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

Closing the vote with 3 +1 and no -1. 3 +1 bindings are: * Nozomi * Hiroyuki * Masahiro Masahiro Sakamoto Yahoo Japan Corp. E-mail: massa...@yahoo-corp.jp -Original Message- From: Masahiro Sakamoto Sent: Monday, December 20, 2021 3:31 PM To: dev@pulsar.apache.org Subject: RE: [VOTE]

Re: [DISCUSSION] PIP-117: Change Pulsar standalone defaults

+1 On Mon, 20 Dec 2021 at 13:42, Lan Liang wrote: > My two cents +1 , In my case, i sometimes need to run pulsar standalone in > some server with limited resources. > > > > Proposed changes > > The other point i can think of is maybe schema storage also need to change > from using BK to usin

[RESULT] [VOTE] Apache Pulsar 2.9.1 candidate 2

Hello everyone, The VOTE passed with 5 VOTEs, 3 of them were binding. - Matteo Merli (binding) - Enrico Olivelli (binding) - Peng Hui (binding) - Nicolò Boschi - Massimiliano Mirelli I will move forward with the next steps https://github.com/apache/pulsar/wiki/Release-process Enrico Il giorno

[DISCUSSION] Produce chunk messages failed when topic level maxMessageSize is set

Hi Pulsar Community, I discovered a bug that chunk messages producing fails if topic level maxMessageSize is set [1]. The root cause of this issue is because chunk message is using broker level maxMessageSize as chunk size. And topic level maxMessageSize is always <= broker level maxMessageSize

[ANNOUNCE] Apache Pulsar Node.js client 1.5.0 released

The Apache Pulsar team is proud to announce Apache Pulsar Node.js client version 1.5.0. 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 mana