This PIP has been updated, and the new design is as compatible with
existing designs as possible, and doesn't depend on
https://github.com/apache/pulsar/pull/23757.
Thanks,
Zixuan
Zixuan Liu 于2024年12月23日周一 16:08写道：
> Hi, Pulsar community,
>
> Subscription replication is an important feature in
This PIP has been updated to adapt to the consumer-level configuration.
Zixuan Liu 于2024年12月23日周一 16:08写道：
> Hi, Pulsar community,
>
> Subscription replication is an important feature in the failover scenario,
> I made a PIP to add the subscription replication feature on the namespace
> and topi
Thanks for your explanation. The users should upgrade the client to
ensure the subscription will be replicated when the namespace or topic
level is set, this is the best practice.
Thanks,
Zixuan
PengHui Li 于2024年12月24日周二 13:03写道：
> > This depends on the consumer's `replicateSubscriptionState` v
> This depends on the consumer's `replicateSubscriptionState` value, when
the
consumer restarts with true or false, this subscription replication
configuration will be reverted, and when there are multiple tenants,
namespace, topic, and subscription, this workload is tedious.
So I mentioned befor
> The reason is we don't have consumer-level control of the replicate
subscription state, it's subscription-level control.
Correct.
> With this solution, you can enable or disable the replicate subscription
state with Admin API for the existing topics/subscriptions.
This depends on the consumer'
In the progress.
Lari Hotari 于2024年12月23日周一 16:20写道：
> This PIP is very useful.
>
> One weakness of this PIP is that it would require client upgrades before it
> would be effective.
> To achieve the desired outcome, I think it would be useful to have a way to
> override the consumer-side setting
Hi Zixuan,
Thanks for bringing the discussion here. After going through the context
and discussions
from https://github.com/apache/pulsar/pull/23770 and
https://github.com/apache/pulsar/pull/23769.
It looks like we can improve the option "replicateSubscriptionState" to
make it only work for the ne
This PIP is very useful.
One weakness of this PIP is that it would require client upgrades before it
would be effective.
To achieve the desired outcome, I think it would be useful to have a way to
override the consumer-side setting and enable subscription replication for
all topics in a namespace,
Hi, Pulsar community,
Subscription replication is an important feature in the failover scenario,
I made a PIP to add the subscription replication feature on the namespace
and topic levels.
PIP: https://github.com/apache/pulsar/pull/23770
Thanks,
Zixuan
