The ability to drain Pulsar Function workers

It is useful to be able to autoscale the number of Pulsar Function workers when configuring the cluster to run instances as threads (ThreadRuntime) in an environment like K8s. When scaling out the number of workers, the "rebalance" endpoint can be involved after the scale out so that the new worke

[GitHub] [pulsar-manager] GPrabhudas opened a new pull request #416: add ui to check topic schema

GPrabhudas opened a new pull request #416: URL: https://github.com/apache/pulsar-manager/pull/416 Fixes #409 ### Motivation ### Modifications *Added ability to view schema registered with topic on UI* ### Verifying this change - [x] Make sure that the

Re: Use JDK11 to release Apache Pulsar 2.8.1

On Tue, Aug 31, 2021 at 9:58 AM Ivan Kelly wrote: > > * Pulsar client should remain on JDK 8 > I'm sure this was discussed in the past, but who is the JDK8 support > being maintained for? > And wouldn't they just continue to use the 2.8 client which does support 8? The effort required to switch

Re: Use JDK11 to release Apache Pulsar 2.8.1

> My doubt here is if that alone is enough of a reason to require users > to switch, or if we should instead wait for JDK 17 and fast track to > that. The biggest thing isn't to get people on to a new one. It's to wean them off of jdk8. jdk11 achieves this. -Ivan

Re: Use JDK11 to release Apache Pulsar 2.8.1

On Tue, Aug 31, 2021 at 9:52 AM Jonathan Ellis wrote: > > Well, it's 9+10+11, so the big one is local type inference from Java 10. Yes, local type inference is nice, but it's definitely not game changing. (eg: if we could use something like value types or green-threads, we could use that to impro

Re: Use JDK11 to release Apache Pulsar 2.8.1

> * Pulsar client should remain on JDK 8 I'm sure this was discussed in the past, but who is the JDK8 support being maintained for? And wouldn't they just continue to use the 2.8 client which does support 8? -Ivan

Re: Use JDK11 to release Apache Pulsar 2.8.1

Well, it's 9+10+11, so the big one is local type inference from Java 10. On Tue, Aug 31, 2021 at 11:12 AM Matteo Merli wrote: > The discussion in the past was around these points: > * Pulsar client should remain on JDK 8 > * We could move server modules to JDK 11 for Pulsar 2.9 > * After JDK

Re: PIP-93 Pulsar Proxy Protocol Handlers

+1, just read through the PIP. Looks good to me. - Michael On Mon, Aug 30, 2021 at 3:47 AM Enrico Olivelli wrote: > Hello Pulsar fellows, > > I have prepared a PIP about adding support for Protocol Handlers > > This is the GDoc > > > https://docs.google.com/document/d/1Hlc_BOpQTkWX8FgrvWSfk6h5x

Re: Use JDK11 to release Apache Pulsar 2.8.1

The discussion in the past was around these points: * Pulsar client should remain on JDK 8 * We could move server modules to JDK 11 for Pulsar 2.9 * After JDK 17 is out for > 6 months, consider moving server modules to 17 The question, right now, is what "source level" features are we missing f

Re: Use JDK11 to release Apache Pulsar 2.8.1

> Sorry for not being clear. My question is, when do we start requiring > JDK11+ so that we can start using newer Java features in the Pulsar code > base? I think this is using jdk11+ for the build and the broker should be fine. The client, and modules depended on by the client may be a different

Re: Use JDK11 to release Apache Pulsar 2.8.1

Sorry for not being clear. My question is, when do we start requiring JDK11+ so that we can start using newer Java features in the Pulsar code base? On Tue, Aug 31, 2021 at 9:23 AM Enrico Olivelli wrote: > Jonathan, > Pulsar 2.8 (and 2.9) builds well on JDK8 and JDK11. > Tests are passing. > De

Fwd: Fw:Re: [Workflow] Introduce Bot to Improve Efficiency

-- Forwarded message - 发件人： tao feng Date: 2021年8月31日周二 下午11:38 Subject: Fwd: Fw:Re: [Workflow] Introduce Bot to Improve Efficiency To: , Thanks for your support! But I have some questions about it. What is a Github bot，（Github app，Github action，or others）？Could you please give

[VOTE] Pulsar Release 2.8.1 Candidate 2

This is the second release candidate for Apache Pulsar, version 2.8.1. It fixes the following issues: https://github.com/apache/pulsar/pulls?q=is%3Apr+label%3Arelease%2F2.8.1+is%3Aclosed *** Please download, test and vote on this release. This vote will stay open for at least 72 hours *** Note t

[GitHub] [pulsar-manager] g0715158 commented on pull request #412: add mysql connector dependent

g0715158 commented on pull request #412: URL: https://github.com/apache/pulsar-manager/pull/412#issuecomment-908832179 > The mysql license is not compatible with the apache license, so it is not recommended to add this Is it appropriate to use mariadb-java-client as a client driver?

[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] 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-908426946 -- 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 unsub

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

nkurihar commented on pull request #168: URL: https://github.com/apache/pulsar-client-node/pull/168#issuecomment-908848586 @Liapin Could you rebase this PR? I have cherry-picked the fix for segmentation fault on tests. https://github.com/apache/pulsar-client-node/pull/170 --

?????? [Workflow] Introduce Bot to Improve Efficiency

Thanks for your support! But I have some questions about it. What is a Github botGithub app??Github action??or othersCould you please give me some information for reference?? Thanks --  -- ??:

Re: Use JDK11 to release Apache Pulsar 2.8.1

Jonathan, Pulsar 2.8 (and 2.9) builds well on JDK8 and JDK11. Tests are passing. Developers can use both JDK8 and JDK11. CI is running ONLY on JDK11 and we have a single workflow that runs some tests on JDK8. The binary tarballs work with JDK8 and JDK11 The Java client works with JDK8 and JDK11 Th

Re: [VOTE] Pulsar Release 2.8.1 Candidate 1

Hello Apache Pulsar Community, Due to the following two issue, 1. check-binary-license failed 2. the source tarball compile failed due to scripts permission I close this vote, and I will start candidate 2 vote soon. Thanks, Hang Enrico Olivelli 于2021年8月31日周二 下午5:56写道： >

Re: Use JDK11 to release Apache Pulsar 2.8.1

What is the plan to fully move to JDK 11 (or JDK 17 which will be released as LTS in two weeks)? I remember Enrico starting a thread in February but I haven't seen an update since then. On Tue, Aug 31, 2021 at 5:15 AM Hang Chen wrote: > Hello Apache Pulsar Community, > In Apache Pulsar 2.8.

[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] 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

Use JDK11 to release Apache Pulsar 2.8.1

Hello Apache Pulsar Community, In Apache Pulsar 2.8.1 RC1, Enrico found "check-binary-license" script fails on the staged tarball ``` ~/dev/pulsar/src/check-binary-license apache-pulsar-2.8.1-bin.tar.gz jetty-alpn-openjdk8-client-9.4.42.v20210604.jar unaccounted for in lib/presto/LICENSE jetty

Re: [VOTE] Pulsar Release 2.8.1 Candidate 1

Hang, thanks for working on the License issue. After working with Hang I realized that the Presto SQL build depends on the JDK you use to build Pulsar. If we build on JDK11 the results are good. The package is still compatible at runtime with JDK8. The problem is about Jetty HTTP2 ALPN Client. Mor

Re: [VOTE] Pulsar Release 2.8.1 Candidate 1

+1 (nonbinding) Built from source code Run distributed system tests with Fallout I had to: chmod +x ./apache-pulsar-2.8.1-src/src/* chmod +x ./apache-pulsar-2.8.1-src/pulsar-client-cpp/docker/* chmod +x docker/pulsar/scripts/* in order to build the package On 2021/08/29 15:23:33, Hang Chen wrot

Re: [Workflow] Introduce Bot to Improve Efficiency

Il giorno mar 31 ago 2021 alle ore 08:28 Anonymitaet _ < anonymita...@hotmail.com> ha scritto: > Hi Pulsar enthusiasts, > > > > Thanks for your support! > > > > Since we have reached a consensus, we are considering implementing Bot to > Pulsar using GitHub Bot