Re: [DISCUSSION] PIP-132: Support Pulsar system event.

Hi, Dave Fisher > These bother me too. Producer and consumers can accomplish the same use cases > in their application logic. > > Any notification mechanism must be very lightweight. What is the implantation > plan? Agree with you. I think we just need to record some system internal event tha

Re: [DISCUSSION] PIP-132: Support Pulsar system event.

Hi, Haiting Jiang >> CompletableFuture trigger(SystemEventMessage message); > > Maybe `record` make more sense? +1 >> SystemEventMessageBuilder properties(Map properties); >> >> SystemEventMessageBuilder addProperty(String key, Object value); > > How to handle the serialization and dese

Re: [DISCUSSION] PIP-132: Support Pulsar system event.

Sent from my iPhone > On Jan 5, 2022, at 8:10 PM, Haiting Jiang wrote: > >  >> CompletableFuture trigger(SystemEventMessage message); > > Maybe `record` make more sense? > >> SystemEventMessageBuilder properties(Map properties); >> >> SystemEventMessageBuilder addProperty(String key,

Re: [DISCUSSION] PIP-132: Support Pulsar system event.

> CompletableFuture trigger(SystemEventMessage message); Maybe `record` make more sense? > SystemEventMessageBuilder properties(Map properties); > > SystemEventMessageBuilder addProperty(String key, Object value); How to handle the serialization and deserialization if the value type i

Re: [ANNOUNCE] New Committer: Zhangjian He

Kudos to Zhangjian! And thanks for your documentation contribution, welcome to submit more commits! On Thu, Jan 6, 2022 at 10:20 AM Haiting Jiang wrote: > Congrats, Zhangjian! > > Thanks, > Haiting Jiang > > On 2022/01/06 02:05:53 Jia Zhai wrote: > > Congratulations to Zhangjian! > > Thanks for

Re: [ANNOUNCE] New Committer: Zhangjian He

Congrats, Zhangjian! Thanks, Haiting Jiang On 2022/01/06 02:05:53 Jia Zhai wrote: > Congratulations to Zhangjian! > Thanks for your contributions to Pulsar. > > > > On Thu, Jan 6, 2022 at 9:25 AM guo jiwei wrote: > > > Congrats to Zhangjian! > > > > > > Regards > > Jiwei Guo (Tboy) > > > > >

Re: [ANNOUNCE] New Committer: Zhangjian He

Congratulations to Zhangjian! Thanks for your contributions to Pulsar. On Thu, Jan 6, 2022 at 9:25 AM guo jiwei wrote: > Congrats to Zhangjian! > > > Regards > Jiwei Guo (Tboy) > > > On Wed, Jan 5, 2022 at 10:59 PM Hang Chen wrote: > > > The Apache Pulsar Project Management Committee (PMC) ha

Re: [ANNOUNCE] New Committer: Zhangjian He

Congrats to Zhangjian! Regards Jiwei Guo (Tboy) On Wed, Jan 5, 2022 at 10:59 PM Hang Chen wrote: > The Apache Pulsar Project Management Committee (PMC) has invited Zhangjian > He > https://github.com/Shoothzj to become a committer and we are pleased to > announce that he has accepted. > > Zha

Re: [DISCUSS] Apache Pulsar 2.9.2 release

+1 Regards Jiwei Guo (Tboy) On Thu, Jan 6, 2022 at 2:32 AM Michael Marshall wrote: > +1 - thanks for starting this thread. > > >171 commits? > > Why? > > This is too much in my opinion for a point release. > > I agree that this is a lot of commits, and especially since we only > just released

[GitHub] [pulsar-client-node] Hoskins355 commented on issue #188: When installing the Pulsar Node.js client, the operation steps need to be optimized

Hoskins355 commented on issue #188: URL: https://github.com/apache/pulsar-client-node/issues/188#issuecomment-1006180927 I am facing the same. @zhaoyajun2009 did you get it working? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to G

[DISCUSSION] PIP-133 Pulsar Functions Add API For Accessing Other Function States

Original PIP: https://github.com/apache/pulsar/issues/13633 Pasted below for quoting convenience. - ## Motivation Certain uses of Pulsar functions could benefit from the ability to access the states of other functions. Currently functions can only access their own states, and so sharing i

[GitHub] [pulsar-helm-chart] michaeljmarshall commented on a change in pull request #130: Bump pulsar 2.8.0

michaeljmarshall commented on a change in pull request #130: URL: https://github.com/apache/pulsar-helm-chart/pull/130#discussion_r779156795 ## File path: charts/pulsar/values.yaml ## @@ -278,7 +278,7 @@ zookeeper: replicaCount: 3 updateStrategy: type: RollingUpdate

Re: [DISCUSS] Remove Grafana and Prometheus Dockerfiles; Remove DCOS example

Here is the PR to remove the DC/OS example: https://github.com/apache/pulsar/pull/13632 In the PR, I remove the `site2/docs/deploy-dcos.md` file, as it won't have much meaning without the underlying example. Further, it contains 5 broken links to Streamlio's GitHub repo (the repo no longer exists)

Re: [PR] Pulsar non root docker image

PR 13376 is ready for review, PTAL. What approach should we take regarding docker image size? I propose providing a minimal image along with documentation on how to add your own debugging tools. Is that sufficient? I'd like to include this feature in 2.10.0. Note that you can test the new docker

Re: [DISCUSS] Apache Pulsar 2.9.2 release

+1 - thanks for starting this thread. >171 commits? > Why? > This is too much in my opinion for a point release. I agree that this is a lot of commits, and especially since we only just released 2.9.1. Note though that this is not a new phenomenon: 2.8.2 had 251 commits on top of 2.8.1. [0] > Ev

Re: [DISCUSSION] PIP-121: Pulsar cluster level auto failover

I am commeting on the GH issue Thanks Enrico Il Mer 5 Gen 2022, 04:56 PengHui Li ha scritto: > +1 > > Penghui > > On Tue, Jan 4, 2022 at 4:51 PM Hang Chen wrote: > > > https://github.com/apache/pulsar/issues/13315 > > > > Pasted below for quoting convenience. > > > > > > ### Motivation >

Re: [DISCUSS] Apache Pulsar 2.9.2 release

BTW +1 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 Enrico Thank you Ran Gao for starting this thread.

[GitHub] [pulsar-helm-chart] michaeljmarshall commented on issue #167: Pulsar minikube installation pods fail

michaeljmarshall commented on issue #167: URL: https://github.com/apache/pulsar-helm-chart/issues/167#issuecomment-1005909843 @pancudaniel7 - can you provide a bit more context? When you describe the pods that are in a "freeze state", do they have any kubernetes events? Does it work event

[GitHub] [pulsar-helm-chart] michaeljmarshall commented on issue #184: Helm Chart installs Pulsar Manager V1.0

michaeljmarshall commented on issue #184: URL: https://github.com/apache/pulsar-helm-chart/issues/184#issuecomment-1005907480 @SapnaGirdhani1 - you can configure the version of the pulsar manager by adding the following to your helm values file: ```yaml pulsar_manager: tag:

[GitHub] [pulsar-helm-chart] michaeljmarshall closed issue #184: Helm Chart installs Pulsar Manager V1.0

michaeljmarshall closed issue #184: URL: https://github.com/apache/pulsar-helm-chart/issues/184 -- 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: de

[GitHub] [pulsar-helm-chart] michaeljmarshall commented on issue #156: chage the pulsar-manager port

michaeljmarshall commented on issue #156: URL: https://github.com/apache/pulsar-helm-chart/issues/156#issuecomment-1005903379 I provided an answer to this issue here: https://github.com/apache/pulsar/issues/11909#issuecomment-917219256. It is not possible to configure the node port to 810

[GitHub] [pulsar-helm-chart] michaeljmarshall commented on issue #185: Github Actions should enforce an increase in helm chart semantic version on each PR

michaeljmarshall commented on issue #185: URL: https://github.com/apache/pulsar-helm-chart/issues/185#issuecomment-1005897271 I think a release for every change would lead to too many releases. However, there is an underlying problem that this issue points to: contributors to the helm cha

Re: [DISCUSS] Apache Pulsar 2.9.2 release

171 commits? Why? This is too much in my opinion for a point release. I am pretty sure that we don't need all that changes. Every change we cherry pick has a good chance to break the stability Enrico Il Mer 5 Gen 2022, 16:30 mattison chao ha scritto: > +1 > > regards, > Mattisonchao > > On

[GitHub] [pulsar-helm-chart] michaeljmarshall closed issue #148: Add the ability to specify a custom command to the start up process of statefulset pods

michaeljmarshall closed issue #148: URL: https://github.com/apache/pulsar-helm-chart/issues/148 -- 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: de

[GitHub] [pulsar-helm-chart] michaeljmarshall merged pull request #150: added additionalCommand parameter

michaeljmarshall merged pull request #150: URL: https://github.com/apache/pulsar-helm-chart/pull/150 -- 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-mai

[GitHub] [pulsar-helm-chart] michaeljmarshall commented on pull request #150: added additionalCommand parameter

michaeljmarshall commented on pull request #150: URL: https://github.com/apache/pulsar-helm-chart/pull/150#issuecomment-1005876996 This PR adds value, even though the original goal of this feature might break when we move to a non-root docker image, so I am going to merge it now. -- Thi

[GitHub] [pulsar-helm-chart] michaeljmarshall commented on pull request #176: Fix cluster initialize blocked when fail: #175

michaeljmarshall commented on pull request #176: URL: https://github.com/apache/pulsar-helm-chart/pull/176#issuecomment-1005874420 > I think it's useful to have multiple PRs batched into a release. +1 -- This is an automated message from the Apache Git Service. To respond to the

Re: [DISCUSS] Apache Pulsar 2.9.2 release

+1 regards, Mattisonchao On Wed, 5 Jan 2022 at 23:04, Lan Liang wrote: > +1,Thanks for your work. > > > > > > > Best Regards, > Lan Liang > On 1/5/2022 23:01，Hang Chen wrote： > +1 > > Best, > Hang > > 陳智弘 于2022年1月5日周三 21:30写道： > > +1 > > Lari Hotari 於 2022年1月5日 週三 20:56 寫道： > > +1 > > On Wed,

[DISCUSSION] PIP-132: Support Pulsar system event.

Original PIP : https://github.com/apache/pulsar/issues/13628 Pasted bellow for quoting convenience. —— ## Motivation In some case or for better observability. We can support Pulsar event notification mechanism, that can let user subscribe this system topic to receive some **"we need notice t

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

+1 Best Regards, Lan Liang On 12/23/2021 19:21，Haiting Jiang wrote： +1 Thanks, Haiting On 2021/12/23 05:35:03 Michael Marshall wrote: +1 - Michael On Wed, Dec 22, 2021 at 6:18 PM Sijie Guo wrote: +1 On Tue, Dec 21, 2021 at 3:49 PM Matteo Merli wrote: This is the voting thread for PI

[GitHub] [pulsar-helm-chart] frankjkelly commented on pull request #176: Fix cluster initialize blocked when fail: #175

frankjkelly commented on pull request #176: URL: https://github.com/apache/pulsar-helm-chart/pull/176#issuecomment-1005771570 @lhotari Sounds good, thanks for the clarification. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHu

Re: [DISCUSS] Apache Pulsar 2.9.2 release

+1,Thanks for your work. Best Regards, Lan Liang On 1/5/2022 23:01，Hang Chen wrote： +1 Best, Hang 陳智弘 于2022年1月5日周三 21:30写道： +1 Lari Hotari 於 2022年1月5日 週三 20:56 寫道： +1 On Wed, Jan 5, 2022 at 11:23 AM Ran Gao wrote: Hello, Pulsar community: I'd like to propose that we release Apache

Re: [DISCUSS] Apache Pulsar 2.9.2 release

+1 Best, Hang 陳智弘 于2022年1月5日周三 21:30写道： > > +1 > > Lari Hotari 於 2022年1月5日 週三 20:56 寫道： > > > +1 > > > > On Wed, Jan 5, 2022 at 11:23 AM Ran Gao wrote: > > > > > Hello, Pulsar community: > > > > > > I'd like to propose that we release Apache Pulsar 2.9.2. > > > > > > Currently, compared to 2.9

[ANNOUNCE] New Committer: Zhangjian He

The Apache Pulsar Project Management Committee (PMC) has invited Zhangjian He https://github.com/Shoothzj to become a committer and we are pleased to announce that he has accepted. Zhangjian He has joined the community for more than 1 year now and he is active in the Pulsar community for more than

[GitHub] [pulsar-helm-chart] lhotari commented on pull request #176: Fix cluster initialize blocked when fail: #175

lhotari commented on pull request #176: URL: https://github.com/apache/pulsar-helm-chart/pull/176#issuecomment-1005734036 > @lhotari without a change in Chart version will a new release be created? CC: @sijie correct. Here's the logs: https://github.com/apache/pulsar-helm-chart/run

[GitHub] [pulsar-helm-chart] frankjkelly commented on pull request #176: Fix cluster initialize blocked when fail: #175

frankjkelly commented on pull request #176: URL: https://github.com/apache/pulsar-helm-chart/pull/176#issuecomment-1005731034 @lhotari without a change in Chart version will a new release be created? CC: @sijie -- This is an automated message from the Apache Git Service. To respond to

[GitHub] [pulsar-helm-chart] lhotari merged pull request #181: Add ability to run extra commands in the initialization jobs e.g. to quit istio sidecars

lhotari merged pull request #181: URL: https://github.com/apache/pulsar-helm-chart/pull/181 -- 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: dev-un

[ANNOUNCE] Apache Pulsar 2.8.2 released

The Apache Pulsar team is proud to announce Apache Pulsar version 2.8.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, automatic cursor management for subsc

[GitHub] [pulsar-helm-chart] lhotari merged pull request #176: Fix cluster initialize blocked when fail: #175

lhotari merged pull request #176: URL: https://github.com/apache/pulsar-helm-chart/pull/176 -- 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: dev-un

[GitHub] [pulsar-helm-chart] lhotari closed issue #175: Create may block if the initialize cluster job fails

lhotari closed issue #175: URL: https://github.com/apache/pulsar-helm-chart/issues/175 -- 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: dev-unsubsc

[GitHub] [pulsar-helm-chart] lhotari merged pull request #138: automate initialize

lhotari merged pull request #138: URL: https://github.com/apache/pulsar-helm-chart/pull/138 -- 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: dev-un

[GitHub] [pulsar-helm-chart] lhotari closed issue #114: Use hooks instead of initialize=true

lhotari closed issue #114: URL: https://github.com/apache/pulsar-helm-chart/issues/114 -- 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: dev-unsubsc

Re: upcoming change: Apache Pulsar Helm Chart switching from Pulsar 2.7.4 version to 2.8.2; known issue with ZK when TLS is enabled

Hi everyone, From my side, I think currently merging the request without regarding the known issue and announcing this information on the website is a good option. 不含病毒。www.avg.com <

[GitHub] [pulsar-helm-chart] valeriano-manassero commented on pull request #138: automate initialize

valeriano-manassero commented on pull request #138: URL: https://github.com/apache/pulsar-helm-chart/pull/138#issuecomment-1005708870 > @valeriano-manassero Thank you for the contribution. Would it be also possible to update README.md in this PR and remove the instructions of using `--set

Re: [DISCUSS] Apache Pulsar 2.9.2 release

+1 Lari Hotari 於 2022年1月5日 週三 20:56 寫道： > +1 > > On Wed, Jan 5, 2022 at 11:23 AM Ran Gao wrote: > > > Hello, Pulsar community: > > > > I'd like to propose that we release Apache Pulsar 2.9.2. > > > > Currently, compared to 2.9.1, branch-2.9 already merged 171 commits(refer > > to [0]), they con

[GitHub] [pulsar-helm-chart] haorenfsa commented on pull request #176: Fix cluster initialize blocked when fail: #175

haorenfsa commented on pull request #176: URL: https://github.com/apache/pulsar-helm-chart/pull/176#issuecomment-1005682255 updated -- 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

Re: upcoming change: Apache Pulsar Helm Chart switching from Pulsar 2.7.4 version to 2.8.2; known issue with ZK when TLS is enabled

Reminder: we need to decide about the developement of Apache Pulsar Helm chart. Please reply to the email or review https://github.com/apache/pulsar-helm-chart/pull/190 . That PR is blocked since a decision must be made whether it's fine to make the change, although there's a known issue in Zookeep

Re: [DISCUSS] Apache Pulsar 2.9.2 release

+1 On Wed, Jan 5, 2022 at 11:23 AM Ran Gao wrote: > Hello, Pulsar community: > > I'd like to propose that we release Apache Pulsar 2.9.2. > > Currently, compared to 2.9.1, branch-2.9 already merged 171 commits(refer > to [0]), they contain the log4j security patch and many important fixes. > > I

Re: Lifting Kubernetes minimum version requirement for Apache Pulsar Helm Charts from k8s 1.14 to 1.18

Reminder, there's a PR to lift the minimum requirement for Apache Pulsar Helm Charts to 1.18 so that we don't fall too far behind. https://github.com/apache/pulsar-helm-chart/pull/192 Please review BR, Lari On Tue, Jan 4, 2022 at 11:40 AM Lari Hotari wrote: > Hi all, > > Currently k8s 1.14 vers

[GitHub] [pulsar-helm-chart] lhotari closed pull request #196: [CI] Remove --ignore-errors=true parameter which requires newer kubectl

lhotari closed pull request #196: URL: https://github.com/apache/pulsar-helm-chart/pull/196 -- 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: dev-un

[GitHub] [pulsar-helm-chart] lhotari commented on pull request #196: [CI] Remove --ignore-errors=true parameter which requires newer kubectl

lhotari commented on pull request #196: URL: https://github.com/apache/pulsar-helm-chart/pull/196#issuecomment-1005645719 It turns out that the current version of kubectl doesn't support `--prefix=true` which adds the pod name and container name as a prefix to each log line. It's better t

[GitHub] [pulsar-helm-chart] lhotari opened a new pull request #196: [CI] Remove --ignore-errors=true parameter which requires newer kubectl

lhotari opened a new pull request #196: URL: https://github.com/apache/pulsar-helm-chart/pull/196 - #192 changes with upgraded kubectl version would be required unless the parameter is removed -- This is an automated message from the Apache Git Service. To respond to the message, ple

[GitHub] [pulsar-helm-chart] lhotari commented on pull request #138: automate initialize

lhotari commented on pull request #138: URL: https://github.com/apache/pulsar-helm-chart/pull/138#issuecomment-1005614211 @valeriano-manassero Thank you for the contribution. Would it be also possible to update README.md in this PR and remove the instructions of using `--set initialize=tr

Re: [DISCUSS] Apache Pulsar 2.9.2 release

+1 Thanks, Penghui On Wed, Jan 5, 2022 at 5:23 PM Ran Gao wrote: > Hello, Pulsar community: > > I'd like to propose that we release Apache Pulsar 2.9.2. > > Currently, compared to 2.9.1, branch-2.9 already merged 171 commits(refer > to [0]), they contain the log4j security patch and many import

[DISCUSS] Apache Pulsar 2.9.2 release

Hello, Pulsar community: I'd like to propose that we release Apache Pulsar 2.9.2. Currently, compared to 2.9.1, branch-2.9 already merged 171 commits(refer to [0]), they contain the log4j security patch and many important fixes. I am happy to volunteer to be the release manager. I see 4 merged

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: Apply redelivery backoff policy for

Re: [DISCUSSION] PIP-132: Include message header size when check maxMessageSize of non-batch message on the client side.

> as we have the same header size for each chunk message. The message metadata of different chunks will not be the same. There are serval fields with different values such as chunk id, publish time. Because some type of that fields is varint, I think the size of the header is not always the same.