Your shared steps are not using global configuration store and both US-EAST and US-WEST are using their own zk cluster as the configuration store.
To deploy with a global configuration store, you may need to follow: 1. Use a separate helm release to provision a zk-only cluster. 2. When provisioning the US-EAST and US-WEST should specify the configurationStore address as the separate zk cluster by https://github.com/apache/pulsar-helm-chart/blob/master/charts/pulsar/values.yaml#L657 This deploy will make the US-EAST and US-WEST to their local zk cluster as the metadata store and the separate zk cluster as the configuration store. Geo Replication can still work without the support of the global configuration store, and you just need to make that when you create a new namespace or topic that needs to be replicated, you should run the command `bin/pulsar-admin topics create my-tenant/my-namespace/my-topic --clusters east-region-pulsar,west-region-pulsar` on both clusters first then to try with the produce and consume. --- Best regards, Eric Shen 在 2023年8月31日 +0800 PM6:23，Sathiskumar Perumal <sathiskumarperumalj...@gmail.com>，写道： > > I have executed the following commands. PFA. > I have separate PODs for each cluster and enabled Geo replication. > Can you please elaborate about the Global Configuration store or the cluster > flag settings, if there is no global configuration store. > Would you please check the document and let me know what is missing in my > configuration?
