Hi Rajan,
Thanks for sharing the link! I will follow the PR.
Best Regards,
Nikolai
On 2023/12/02 01:21:04 Rajan Dhabalia wrote:
> Hi Nikolai,
>
> I completely understand your concern and pain. But let's understand
> ordering semantics for exclusive/fail-over subscription. This
subscription
Hi Nikolai,
I completely understand your concern and pain. But let's understand
ordering semantics for exclusive/fail-over subscription. This subscription
makes sure to dispatch new messages which the broker is reading using
readPosition must be in order but that doesn't mean the broker will never
Hi Rajan,
Thanks for the review!
It looks like the root cause of "stuck" keyword is the nature of
Key_Shared subscription which must guarantee messages ordering. I
understand it is really hard to achieve such guarantees without having
separate physical partitions but this feature is very esse
Hi Nikolai,
Thanks for bringing this to the attention. I have seen multiple PIP and bug
fixes for the Key-Shared subscription and I feel Key_Shared subscription
dispatcher is developed with multiple fundamental issues which required to
introduce scheduled-task to unblock stuck reads, introducing s
Hi Nikolai - Your email was stuck in moderation. Please subscribe to the dev
list by sending an email to dev-subscr...@pulsar.apache.org and respond to the
CONFIRM email.
Welcome to the Pulsar community.
Best,
Dave
> On Nov 28, 2023, at 10:30 PM, Nikolai wrote:
>
> Hello!
>
> I submitted a
Hello!
I submitted a new PIP to add a configuration option which allows to skip
blocking recently joined consumers for Key_Shared subscriptions
It introduces additional memory consumption, so it will be disabled by
default. It would fix issues like
https://github.com/apache/pulsar/issues/211
