AlvaroStream opened a new issue, #18016: URL: https://github.com/apache/pulsar/issues/18016
### Search before asking - [X] I searched in the [issues](https://github.com/apache/pulsar/issues) and found nothing similar. ### What issue do you find in Pulsar docs? Explanation from the [replication clusters](https://pulsar.apache.org/docs/administration-geo/#connect-replication-clusters ) could be improved, after reading several times the geo-replication I was a little bit lost. ### What is your suggestion? - I think the first example should be just between 2 clusters. And put an example with more differences in the names. Sometimes it is difficult to follow `us-west`, `us-cent`, and `us-east` clusters. I would rename them to Original and Replicated. - There could be another second example with 3 clusters but easier to follow. - I missed in the explanation of geo-replication that replication behaves like a “subscription” in Cluster Origin that connect as a producer into Cluster Replica. So that explains what happens on next command, why you execute it in Origin and the information you need to provide. ``` $ bin/pulsar-admin clusters create \ --broker-url pulsar://<DNS-OF-REPLICA>:<PORT> \ --url http://<DNS-OF-REPLICA>:<PORT> \ replica-cluster ``` ### Any reference? N/A ### Are you willing to submit a PR? - [X] I'm willing to submit a PR! -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
