Hi Xiangying,
Shouldn't the solution to the issue mentioned in #21564 [0] mostly be
around validating that topic level replication clusters are subset of
namespace level replication clusters?
It would be a completely compatible change as even today the case where a
topic has a cluster not defined
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,
I don't agree with your assumptions about allowed clusters and
replication-cluster definition. Allowed clusters defined at tenant level
will restrict tenants to create namespaces in regions/clusters where they
are not allowed. and replication clusters will help tenant to set up full
mesh repli
Hi, yubiao.
Thanks for your feedback.
After discussing with Penghui, we need to wait for the Bookkeeper 4.15.5
release and then upgrade it on Pulsar.
So, close this Vote first.
Thanks,
Baodi Shi
On Nov 29, 2023 at 12:09:00, Yubiao Feng
wrote:
> Hi Penghui, Baodi
>
> - Run standalone and che
Hi All,
I am closing the vote as we have 4 binding +1's:
- Yubiao Feng
- Lari Hotari
- Matteo Merli
- Qiang Zhao
And 3 non-binding +1's:
- Apurva Telang
- Cong Zhao
- Kai Wang
Thanks everyone!
Regards,
Kevin
On Wed, Nov 29, 2023 at 4:25 PM Kai Wang wrote:
> +1 (non-binding)
>
> Thanks,
> Kai
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
Hello,
I have filed the following issue which is an unexpected and unhandled exception
that terminates our application, full details in the issue.
>From looking at the code it appears the likely location for the exception is
>the std::recursive_mutex.
It is not clear to us why this exception wou
Hi Team,
Any updates on including transaction support on C++ client ?
Thanks & Regards
Karthikeyan A
-Original Message-
From: Yunze Xu
Sent: 17 May 2023 08:33
To: dev@pulsar.apache.org
Subject: Re: [ANNOUNCE] Apache Pulsar Client C++ 3.2.0 released
I have a plan to support the transac