You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@pulsar.apache.org by Yuri Mizushima <eq...@apache.org> on 2023/11/28 08:03:51 UTC
[VOTE] PIP-282: Change definition of the recently joined consumers position
Hi, Pulsar Community
This thread is starting a vote for PIP-282.
PIP design PR:
https://github.com/apache/pulsar/pull/20776
discussion thread:
https://lists.apache.org/thread/69fpb0d30y7pc02k3zvg2lpb2lj0smdg
Motivation
Key_Shared has a mechanism called the "recently joined consumers" to keep
message ordering.
However, currently, it doesn't care about some corner cases.
1. [issue-1] The race condition in the "recently joined consumers", where
consumers can be added before finishing reading and dispatching messages
from ledgers.
2. [issue-2] Messages could be added to messagesToRedeliver without
consumer-side operations such as unacknowledgement.
We should care about these cases in Key_Shared subscription.
Thanks,
--
Yuri Mizushima
equanz@apache.org
Re: [VOTE] PIP-282: Change definition of the recently joined consumers position
Posted by Nozomi Kurihara <nk...@apache.org>.
+1
Thanks,
Nozomi
2023年11月28日(火) 17:04 Yuri Mizushima <eq...@apache.org>:
> Hi, Pulsar Community
>
> This thread is starting a vote for PIP-282.
>
> PIP design PR:
> https://github.com/apache/pulsar/pull/20776
>
> discussion thread:
> https://lists.apache.org/thread/69fpb0d30y7pc02k3zvg2lpb2lj0smdg
>
> Motivation
>
> Key_Shared has a mechanism called the "recently joined consumers" to keep
> message ordering.
> However, currently, it doesn't care about some corner cases.
>
> 1. [issue-1] The race condition in the "recently joined consumers", where
> consumers can be added before finishing reading and dispatching messages
> from ledgers.
> 2. [issue-2] Messages could be added to messagesToRedeliver without
> consumer-side operations such as unacknowledgement.
>
> We should care about these cases in Key_Shared subscription.
>
> Thanks,
>
> --
> Yuri Mizushima
> equanz@apache.org
>
Re: [VOTE] PIP-282: Change definition of the recently joined consumers position
Posted by Yuri Mizushima <eq...@apache.org>.
Close this vote by 3 binding +1.
Thanks,
--
Yuri Mizushima
equanz@apache.org
On 2023/12/19 11:10:45 PengHui Li wrote:
> +1
>
> Thanks,
> Penghui
>
> On Tue, Dec 19, 2023 at 3:58 PM Yubiao Feng
> <yu...@streamnative.io.invalid> wrote:
>
> > +1
> >
> > Thanks
> > Yubiao Feng
> >
> > On Tue, Nov 28, 2023 at 4:04 PM Yuri Mizushima <eq...@apache.org> wrote:
> >
> > > Hi, Pulsar Community
> > >
> > > This thread is starting a vote for PIP-282.
> > >
> > > PIP design PR:
> > > https://github.com/apache/pulsar/pull/20776
> > >
> > > discussion thread:
> > > https://lists.apache.org/thread/69fpb0d30y7pc02k3zvg2lpb2lj0smdg
> > >
> > > Motivation
> > >
> > > Key_Shared has a mechanism called the "recently joined consumers" to keep
> > > message ordering.
> > > However, currently, it doesn't care about some corner cases.
> > >
> > > 1. [issue-1] The race condition in the "recently joined consumers", where
> > > consumers can be added before finishing reading and dispatching messages
> > > from ledgers.
> > > 2. [issue-2] Messages could be added to messagesToRedeliver without
> > > consumer-side operations such as unacknowledgement.
> > >
> > > We should care about these cases in Key_Shared subscription.
> > >
> > > Thanks,
> > >
> > > --
> > > Yuri Mizushima
> > > equanz@apache.org
> > >
> >
>
Re: [VOTE] PIP-282: Change definition of the recently joined consumers position
Posted by PengHui Li <pe...@apache.org>.
+1
Thanks,
Penghui
On Tue, Dec 19, 2023 at 3:58 PM Yubiao Feng
<yu...@streamnative.io.invalid> wrote:
> +1
>
> Thanks
> Yubiao Feng
>
> On Tue, Nov 28, 2023 at 4:04 PM Yuri Mizushima <eq...@apache.org> wrote:
>
> > Hi, Pulsar Community
> >
> > This thread is starting a vote for PIP-282.
> >
> > PIP design PR:
> > https://github.com/apache/pulsar/pull/20776
> >
> > discussion thread:
> > https://lists.apache.org/thread/69fpb0d30y7pc02k3zvg2lpb2lj0smdg
> >
> > Motivation
> >
> > Key_Shared has a mechanism called the "recently joined consumers" to keep
> > message ordering.
> > However, currently, it doesn't care about some corner cases.
> >
> > 1. [issue-1] The race condition in the "recently joined consumers", where
> > consumers can be added before finishing reading and dispatching messages
> > from ledgers.
> > 2. [issue-2] Messages could be added to messagesToRedeliver without
> > consumer-side operations such as unacknowledgement.
> >
> > We should care about these cases in Key_Shared subscription.
> >
> > Thanks,
> >
> > --
> > Yuri Mizushima
> > equanz@apache.org
> >
>
Re: [VOTE] PIP-282: Change definition of the recently joined consumers position
Posted by Yubiao Feng <yu...@streamnative.io.INVALID>.
+1
Thanks
Yubiao Feng
On Tue, Nov 28, 2023 at 4:04 PM Yuri Mizushima <eq...@apache.org> wrote:
> Hi, Pulsar Community
>
> This thread is starting a vote for PIP-282.
>
> PIP design PR:
> https://github.com/apache/pulsar/pull/20776
>
> discussion thread:
> https://lists.apache.org/thread/69fpb0d30y7pc02k3zvg2lpb2lj0smdg
>
> Motivation
>
> Key_Shared has a mechanism called the "recently joined consumers" to keep
> message ordering.
> However, currently, it doesn't care about some corner cases.
>
> 1. [issue-1] The race condition in the "recently joined consumers", where
> consumers can be added before finishing reading and dispatching messages
> from ledgers.
> 2. [issue-2] Messages could be added to messagesToRedeliver without
> consumer-side operations such as unacknowledgement.
>
> We should care about these cases in Key_Shared subscription.
>
> Thanks,
>
> --
> Yuri Mizushima
> equanz@apache.org
>