nodece commented on PR #21679: URL: https://github.com/apache/pulsar/pull/21679#issuecomment-1876497100
> And for clusters with multiple configuration stores, users need to create the partitioned topic to multiple clusters manually. @codelipenghui Sure, I agree with you. Usually, users need to create the topic on the remote clusters manually. > For creating the partitioned topics to the remote cluster. We might also need to take the security issues into consideration, the credential to access the remote cluster should not always be the super user . And different clusters might have different limitations, e.g. max topics. This kind of behavior has existed for a long time, perhaps we did not consider max topics. When the GEO is enabled on the namespace level, you create the topic on the local cluster, the broker also creates the topic on the remote cluster, please see: https://github.com/apache/pulsar/blob/44a07542e9472363588b1c4146f6371bf4997c32/pulsar-broker/src/main/java/org/apache/pulsar/broker/admin/AdminResource.java#L676-L690 > And there is another https://github.com/apache/pulsar/issues/16424 to sync the configuration store events across different clusters. I think it should be a related topic? #16424 is used to sync all configuration store to another cluster. For my case, I only sync some topic to another cluster by the GEO. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: commits-unsubscr...@pulsar.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
