Dear Pulsar Community,
I am excited to announce that the first PR implementing "PIP-379:
Key_Shared Draining Hashes for Improved Message Ordering" is now ready
for review. This PR contains the core implementation as described in
the PIP-379 document. PIP-379 is currently in voting.
Since there is
>> Is this the correct understanding of how PR 9292 efficiently stores
individual acks?
Yes, that's correct. It's like serializing a Position object to a bit which
could be the smallest serializable size we could achieve among any ser/des
approaches.
In the past, there were two fundamental challe
+1 (non-binding)
Best regards,
Apurva Telang.
On Wed, Oct 2, 2024 at 00:32 Enrico Olivelli wrote:
> +1 (binding)
>
>
> Enrico
>
> Il Mer 2 Ott 2024, 03:21 Matteo Merli ha scritto:
>
> > +1
> > --
> > Matteo Merli
> >
> >
> >
> > On Tue, Oct 1, 2024 at 4:53 PM Lari Hotari wrote:
> >
> > > Hi
+1 (binding)
Regards,
Penghui
On Tue, Oct 1, 2024 at 11:36 PM Enrico Olivelli wrote:
> +1 (binding)
>
> Enrico
>
> Il Mer 2 Ott 2024, 03:21 Matteo Merli ha scritto:
>
> > +1
> > --
> > Matteo Merli
> >
> >
> >
> > On Tue, Oct 1, 2024 at 5:03 PM Rajan Dhabalia
> > wrote:
> >
> > > +1 (binding
+1
Thanks
Il gio 3 ott 2024, 02:36 Apurva Telang ha
scritto:
> +1 (non-binding)
>
> Best regards,
> Apurva Telang.
>
>
> On Wed, Oct 2, 2024 at 00:32 Enrico Olivelli wrote:
>
> > +1 (binding)
> >
> >
> > Enrico
> >
> > Il Mer 2 Ott 2024, 03:21 Matteo Merli ha
> scritto:
> >
> > > +1
> > > --
> we might be able to solve storing > 10M-100M unack
messages but the question is if a broker really has that many unack
messages then will broker run with such huge memory pressure and will it
really serve large scale usecases for which Pulsar was built? I am sure, it
might be useful for small use
