Hello all,
The vote to release Apache Pulsar Helm Chart version 3.1.0 based on
3.1.0-candidate-1 is now closed.
The vote PASSED with 3 binding "+1", 0 non-binding "+1" and 0 "-1" votes:
"+1" Binding votes:
- PengHui Li
- Lari Hotari
- Michael Marshall
I'll continue with the release proc
+1 (binding)
- verified signatures are valid on 2 artifacts
- verified checksums are correct on 2 artifacts
- verified `helm gpg verify pulsar-3.1.0.tgz`
- verified the licenses and notice with `java -jar
/apache-rat-0.15/apache-rat-0.15.jar . -E .rat-excludes`. I noticed
that Lari had trouble, so
This is the second release candidate for Apache Pulsar, version 2.11.3.
It fixes the following issues:
https://github.com/apache/pulsar/pulls?q=is%3Apr+label%3Arelease%2F2.11.3+is%3Aclosed
*** Please download, test and vote on this release. This vote will stay
open for at least 72 hours ***
Note
Are we sure the move to Alpine is worth the extensive performance testing and
the risk of issues? Sticking with a popular glibc image like Temurin,
Ubuntu/Debian, or ubi-minimal (mentioned also in this discussion) seems like a
better path to me, without the risk of glibc vs musl issues. Using Di
Sorry, the PIP had approved, please ignore.
Tao Jiuming 于2023年12月21日周四 04:25写道：
>
> bump
>
> On 2022/11/28 08:47:01 Jiuming Tao wrote:
> > Dear Pulsar Community,
> >
> > Please review and vote on this PIP.
> >
> > PIP link: https://github.com/apache/pulsar/issues/18560
> >
> > Discuss thread:
>
bump
On 2022/11/28 08:47:01 Jiuming Tao wrote:
> Dear Pulsar Community,
>
> Please review and vote on this PIP.
>
> PIP link: https://github.com/apache/pulsar/issues/18560
>
> Discuss thread:
> https://lists.apache.org/thread/z74vcn0yolzzrcc4ftonm9j3nbk4pzxm
>
> Thanks,
> Tao Jiuming
>
> I don't see the topic load issues. The topic loading works fine, and
the producer works fine. But the proposal said it would resolve the topic
load issue, can you reproduce the topic load issue?
Yes, you tried different usecase and not the one which is mentioned in the
PIP. Deleted ledgers
In my understanding, the PIP is for some certain `extreme` conditions. Some
ledgers failing to recover is an event with a very low probability, and it
should be hard to reproduce(unless we delete some ledgers manually).
If we skip these failed-recover ledgers, message production should be able
to
+1 (binding)
Tested with Docker Desktop integrated with k8s v1.27.
- Deployed a cluster by using helm install pulsar
apache-pulsar-dist-dev/pulsar --set affinity.anti_affinity=false
- Tested produce and consume
Regards,
Penghui
On Wed, Dec 20, 2023 at 12:25 AM Lari Hotari wrote:
> +1
>
> - Va
The vote is now closed.
The PIP is approved, with 4 +1 binding votes, by Yubaio, Mattison, Penghui
and Guo.
On Mon, Dec 18, 2023 at 4:55 PM mattison chao
wrote:
> +1(binding)
>
> Best,
> Mattison
>
> > On Dec 13, 2023, at 16:22, Asaf Mesika wrote:
> >
> > Hi,
> >
> > I'm starting the vote for
Hi Rajan,
I tried to test the case that you provided in the proposal.
- Produce messages to a topic
- Unload the topic 5 times to ensure we have some ledgers in the topic
- Delete one ledger by using the bookkeeper shell
- Unload the topic again
- Start to produce messages again, it works
- Start
11 matches
Mail list logo
