Re: [VOTE] Pulsar Release 2.8.1 Candidate 2

Hi @enrico, any reason for https://github.com/apache/pulsar/pull/11852 be a blocker for 2.8.1? It's not a regression introduced in 2.8.1 right? Thanks, Penghui On Thu, Sep 2, 2021 at 2:36 PM Enrico Olivelli wrote: > Hang, > I am not able to reproduce Massimiliano's problem > > These commands pa

Re: [DISCUSS] Contribute "Reactive Streams adapter for the Apache Pulsar Java Client" to the Apache Pulsar project

Lari, this is great work ! +1 for accepting this into the Pulsar project and for accepting new adapters/client libraries. My understanding is that Lari will contribute it as a separate repository. My understanding is that it is fine to create a brand new repository and let it be managed by the Pu

Re: [VOTE] Pulsar Release 2.8.1 Candidate 2

Hang, I am not able to reproduce Massimiliano's problem These commands pass on the stages sources unpacked by the source tarball, on Ubuntu: mvn clean install -DskipTests mvn package -Pdocker -f docker/pom-xml I have performed other tests and everything passed (apart from some flaky test), but gi

Re: [DISCUSS] Contribute "Reactive Streams adapter for the Apache Pulsar Java Client" to the Apache Pulsar project

*My two cents about developing and contributing adapters/connectors for Apache Pulsar. Apache Pulsar was open-sourced with Spark and Storm adapters initially and then such adapter families evolved with multiple other adapters, connectors and IO connectors (sink/source) into apache pulsar git repo.

Re: [DISCUSS] Contribute "Reactive Streams adapter for the Apache Pulsar Java Client" to the Apache Pulsar project

Replies inline below: On Thu, Sep 2, 2021 at 3:37 AM Sijie Guo wrote: > Lari, > > Thank you for bringing this up! > > In general, I would love to see this being accepted to the project. > Thanks! > > However, in the past, there were other language clients contributed to the > project. They we

[Doc] 2.8.2 doc set is available

Hi Pulsarers, Pulsar is moving fast to the next milestone (2.9.0) with several minor releases (2.8.1 & 2.8.2). Now we have doc requirements for 2.8.2, so we’ve generated the doc set for 2.8.2. Here is a gentle reminder: * If you need to update 2.8.2 docs, please go here

Re: The ability to drain Pulsar Function workers

Ivan, thanks for reviewing my proposal. I will answer your questions inline. When a leader fails, does the new leader automatically create a new > assignment, or does it continue with the assignment from the previous > leader? > The new leader will resume scheduling duties with the current set of

Re: [DISCUSS] Contribute "Reactive Streams adapter for the Apache Pulsar Java Client" to the Apache Pulsar project

Lari, Thank you for bringing this up! In general, I would love to see this being accepted to the project. However, in the past, there were other language clients contributed to the project. They were not accepted because the PMC doesn't have enough bandwidth to staff it. https://github.com/apach

Re: PIP-93 Pulsar Proxy Protocol Handlers

I would like to see the clarification between the broker protocol handlers and proxy protocol handlers before moving it to a vote thread. I can see how it will cause confusion for protocol developers. Yunze brought a good idea on KoP. But I don't think that's the right direction. If you can give

Re: PIP-93 Pulsar Proxy Protocol Handlers

Any other comment? I would like to start a VOTE, but I feel we saw too few comments here Please take a look. I believe it will be a good fit for 2.9.0 release, that is going to be released in the end of September Enrico Il Mar 31 Ago 2021, 18:14 Michael Marshall ha scritto: > +1, just read t

[GitHub] [pulsar-client-node] alphara opened a new issue #171: Implement native Node.js pulsar-client

alphara opened a new issue #171: URL: https://github.com/apache/pulsar-client-node/issues/171 We face some issues with the Pulsar Node.js client library, based on the C++ client library: • We have a service that creates pulsar producers for 3 streams, consumers for 3 streams. It rec

Re: [VOTE] Pulsar Release 2.8.1 Candidate 2

The chmod command solved the previously reported issue. However, I got a failure in one of the fallout tests which I would still need time to better investigate. The test creates a topic, spawns a function injecting 1 messages from a data-generator into the topic which is then read by a consum

[DISCUSS] Contribute "Reactive Streams adapter for the Apache Pulsar Java Client" to the Apache Pulsar project

Dear Apache Pulsar community members, I have developed a Reactive Streams adapter for the Apache Pulsar Java Client. It uses Project Reactor as the Reactive Streams implementation. The repository is here: https://github.com/lhotari/reactive-pulsar and library is available in Maven Central: https:

[GitHub] [pulsar-helm-chart] dragonls opened a new pull request #155: Add grafana data persistence support.

dragonls opened a new pull request #155: URL: https://github.com/apache/pulsar-helm-chart/pull/155 Fixes #154 ### Motivation Add pulsar pvc to support grafana data persistence. ### Modifications - Add `grafana-pvc.yaml`. - Add grafana data mount logic in `grafana-

[GitHub] [pulsar-client-node] nkurihar merged pull request #168: Branch 1.3

nkurihar merged pull request #168: URL: https://github.com/apache/pulsar-client-node/pull/168 -- 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-

[GitHub] [pulsar-helm-chart] acesir closed issue #153: Pulsar manager default environment

acesir closed issue #153: URL: https://github.com/apache/pulsar-helm-chart/issues/153 -- 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-unsubscr

[GitHub] [pulsar-helm-chart] dragonls commented on pull request #113: Add multi volume support in bookkeeper.

dragonls commented on pull request #113: URL: https://github.com/apache/pulsar-helm-chart/pull/113#issuecomment-909994110 Could this PR be merged? Is there anything else need to do? @eolivelli -- This is an automated message from the Apache Git Service. To respond to the message, please

[GitHub] [pulsar-helm-chart] acesir commented on issue #153: Pulsar manager default environment

acesir commented on issue #153: URL: https://github.com/apache/pulsar-helm-chart/issues/153#issuecomment-909156527 We resorted to building our own image and modifying the init DB script as the current chart and docker image do not support this functionality. -- This is an automated mess

[GitHub] [pulsar-helm-chart] dragonls opened a new issue #154: Grafana data lost once pod restart.

dragonls opened a new issue #154: URL: https://github.com/apache/pulsar-helm-chart/issues/154 **Is your feature request related to a problem? Please describe.** Now, pulsar-helm-chart use empty dir instead of pv. So once grafana pod restarts, the grafana data lost. **Describe the

Re: [VOTE] Pulsar Release 2.8.1 Candidate 2

Found at least one problem: pulsar docker image doesn't seem to be deployed properly due to a permission problem. Running: chmod +x docker/pulsar/scripts/* Might solve it, I am verifying that now. On Wed, 1 Sept 2021 at 11:08, Massimiliano Mirelli < massimilianomirelli...@gmail.com> wrote: > T

Re: [VOTE] Pulsar Release 2.8.1 Candidate 2

Thank you for sharing this rc. I am running a suite of fallout tests on it, let's see how it goes! Massimiliano On Tue, 31 Aug 2021 at 18:33, Hang Chen wrote: > This is the second release candidate for Apache Pulsar, version 2.8.1. > > It fixes the following issues: > > https://github.com/apac

[GitHub] [pulsar-client-node] nkurihar merged pull request #168: Branch 1.3

nkurihar merged pull request #168: URL: https://github.com/apache/pulsar-client-node/pull/168 -- 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-

Pulsar Flaky test report 2021-09-01 for PR builds in CI

Dear Pulsar community members, Here's a report of the flaky tests in Pulsar CI during the observation period of 2021-08-25 - 2021-09-01 . The full report has been also updated to a Google Sheet, https://docs.google.com/spreadsheets/d/165FHpHjs5fHccSsmQM4beeg6brn-zfUjcrXf6xAu4yQ/edit#gid=0 Test me

Re: The ability to drain Pulsar Function workers

> When the leader receives a request to drain a worker, it must first mark > the worker as in the process to be drained i.e. blacklist the worker so > that no new assignments can be assigned to it. We can perhaps just save the > blacklist in memory. The worker should then create a new scheduling in

[GitHub] [pulsar-helm-chart] dragonls commented on pull request #113: Add multi volume support in bookkeeper.

dragonls commented on pull request #113: URL: https://github.com/apache/pulsar-helm-chart/pull/113#issuecomment-909994110 Could this PR be merged? Is there anything else need to do? @eolivelli -- This is an automated message from the Apache Git Service. To respond to the message, please