Hi Zixuan > The GEO-replication can be enabled on the Namespace and > topic levels. When > GEO-replication is enabled on the namespace level, > it automatically creates > the topic for the remote cluster, but the topic level > misses this feature, > which can cause unexpected problems.
https://github.com/apache/pulsar/pull/22537 has implemented it. Thanks Yubiao Feng On Fri, Mar 22, 2024 at 4:44 PM Zixuan Liu <node...@gmail.com> wrote: > Hi all, > > The GEO-replication can be enabled on the Namespace and topic levels. When > GEO-replication is enabled on the namespace level, it automatically creates > the topic for the remote cluster, but the topic level misses this feature, > which can cause unexpected problems. > > When two clusters use different global configuration metadatastore, the > local cluster has a partitioned topic, and then we enable the > GEO-replication on the topic level, I expect a partitioned topic will be > created on the remote cluster, not a non-partitioned topic. BTW, > `allowAutoTopicCreation` was enabled. > > There are two options: > > 1. When the GEO replication is enabled on the topic level , we can create > the topic for the remote cluster(usually, we have superuser permissions): > https://github.com/apache/pulsar/pull/22203 > 2. When the remote cluster has no topic, stop GEO-replication and throw an > error. > > We also need to consider resource/permission issues, so like the remote > clusters disables topic creation or exceed the maximum number of topics. > > Please let me know your thoughts. > > More contexts: https://github.com/apache/pulsar/pull/21679 (This is an > incorrect implement, but there is more context here.) > > Thanks, > Zixuan >
