Re: [VOTE] Reactive Java client for Apache Pulsar 0.5.1 Candidate 1

+1 (binding) - verified source package checksum and signature. - verified staged maven artifacts by running a test app built with Gradle. -Lari On 2023/12/13 21:58:48 Chris Bo wrote: > Following PIP-205: Reactive Java client for Apache Pulsar ( > https://github.com/apache/pulsar/issues/17335), t

[DISCUSS] Apache Pulsar 3.2.0 release

Hi community, It has been more than three months since the release of 3.1.0. we now have more than 305 commits and 26 PIPs

Re: [VOTE] Reactive Java client for Apache Pulsar 0.5.1 Candidate 1

+1 (non-binding) - verified source package checksum and signature. - verified staged maven artifacts by running a test app built with Gradle. On 2023/12/13 21:58:48 Chris Bo wrote: > Following PIP-205: Reactive Java client for Apache Pulsar ( > https://github.com/apache/pulsar/issues/17335), this

[VOTE] Reactive Java client for Apache Pulsar 0.5.1 Candidate 1

Following PIP-205: Reactive Java client for Apache Pulsar ( https://github.com/apache/pulsar/issues/17335), this is release candidate 1 for the Reactive Java client for Apache Pulsar, version 0.5.1. *** Please download, test and vote on this release. This vote will stay open for at least 72 hours

Re: [DISCUSS] PIP-324: Alpine Docker images

I don't think the compatibility for downstream users is going to be a big problem: 1. Most users don't need to modify the Pulsar image in significant way 2. If they do, they won't be using the "latest" tag, but rather a specific version 3. Users who are dependent on the Ubuntu base image can sta

Re: [DISCUSS] PIP-324: Alpine Docker images

-- Matteo Merli On Wed, Dec 13, 2023 at 8:20 AM Christophe Bornet wrote: > Thanks Matteo for bringing this subject. > > I share the concerns of Lari regarding the move from glibc to musl in > terms of security, performance, compatibility with the JVM. Extensive > performance tests will have to

Re: [DISCUSS] PIP-324: Alpine Docker images

Thanks Matteo for bringing this subject. I share the concerns of Lari regarding the move from glibc to musl in terms of security, performance, compatibility with the JVM. Extensive performance tests will have to be done. Also, last time I tried to use alpine with a Python project, it was a nightma

Re: [DISCUSS] PIP-324: Alpine Docker images

For Kubernetes environments, the DNS caching concerns could be covered by using NodeLocal DNSCache [1]. I wonder if that gets configured by default in cloud provider managed k8s services? -Lari 1 - https://kubernetes.io/docs/tasks/administer-cluster/nodelocaldns/ On 2023/12/13 13:16:45 Lari Ho

Re: [DISCUSS] PIP-324: Alpine Docker images

+1 Before switching to Alpine completely, it would be worth running extensive system tests in production-like environments. Alpine comes with musl, which makes the JVM behave slightly differently. One of the common DNS issues with Alpine was fixed in May 2023 with the Alpine 3.18 release. Alpi

Re: [VOTE] PIP-323: Complete Backlog Quota Telemetry

+1 (binding) Regards Jiwei Guo (Tboy) On Wed, Dec 13, 2023 at 4:23 PM Asaf Mesika wrote: > Hi, > > I'm starting the vote for PIP-323, since it has been reviewed by several > people and all comments have been resolved. > > Reminder: > > PIP-323 is introduced to fill the gap of backlog quota te

Re: [VOTE] Pulsar Release 3.1.2 Candidate 2

+1 (binding) - Checked the signatures - Built from source - Run standalone and check the produce, consume - Verified Cassandra connector - Verified stateful function Regards Jiwei Guo (Tboy) On Sat, Dec 9, 2023 at 2:48 PM houxiaoyu wrote: > This is the second release candidate for Apache Pul

Re: [VOTE] PIP-320: OpenTelemetry Scaffolding

The PIP has been approved by the vote. Summary: 5 binding +1 votes 1 non-binding +1 vote Thanks! Asaf On Mon, Dec 11, 2023 at 9:19 PM Matteo Merli wrote: > +1 > -- > Matteo Merli > > > > On Mon, Dec 11, 2023 at 10:13 AM Apurva Telang > wrote: > > > +1 (non-binding) > > > > On Mon, Dec 11, 2

[VOTE] PIP-323: Complete Backlog Quota Telemetry

Hi, I'm starting the vote for PIP-323, since it has been reviewed by several people and all comments have been resolved. Reminder: PIP-323 is introduced to fill the gap of backlog quota telemetry. It allows the user to know when a time-based backlog quota is about to exceed, and how many times i