>> How do we designate the host broker? Is it manual? How does it work when
the host broker is removed from the cluster?
No, it will not be manual but as I explained earlier a broker which has a
failover consumer to consume remote events will be the publisher for
metadata update. If that broker is
>On my first reading, it wasn't clear if there was only one topic
required for this feature. I now see that the topic is not tied to a
specific tenant or namespace. As such, we can avoid complicated
authorization questions by putting the required event topic(s) into a
"system" tenant and namespace
Thanks for your responses.
> I don't see a need of protobuf for this particular usecase
If no one else feels strongly on this point, I am good with using a POJO.
> It doesn't matter if it's system-topic or not because it's
> configurable and the admin of the system can decide and configure it
>
Please find my response inline.
On Mon, Jan 31, 2022 at 9:17 PM Michael Marshall
wrote:
> I think this is a very appropriate direction to take Pulsar's
> geo-replication. Your proposal is essentially to make the
> inter-cluster configuration event driven. This increases fault
> tolerance and bet
I think this is a very appropriate direction to take Pulsar's
geo-replication. Your proposal is essentially to make the
inter-cluster configuration event driven. This increases fault
tolerance and better decouples clusters.
Thank you for your detailed proposal. After reading through it, I have
som
Hi,
I would like to start a discussion about PIP-136: Sync Pulsar policies
across multiple clouds.
PIP documentation: https://github.com/apache/pulsar/issues/13728
*Motivation*
Apache Pulsar is a cloud-native, distributed messaging framework which
natively provides geo-replication. Many organiza
