This message was deleted.
# general
s
This message was deleted.
y
First, you need to figure out how you can connect from broker@machine1 to broker@machine2, vice versa.
a
do you know how I can do that?
y
I don’t know a quick way. This is network routing thing across two machines.
two machines will need to act like routers (ip_forwarding).
a
Is there a more simple way to connect two replication clusters? I can try to do it on the same machine
I'm just not sure how to get "on" cluster us-west and east like it says in the documentation
y
you can run two standalone clusters in 1 machine (with different ports). they will be in the same docker network.
a
Okay, I tried that way as well. But how do I get "on" the clusters.. I think I'm misunderstanding the documentation: Run the following command on
us-west
.
Copy code
bin/pulsar-admin clusters create \
--broker-url pulsar://<DNS-OF-US-EAST>:<PORT> \
--url http://<DNS-OF-US-EAST>:<PORT> \
us-east
So I just run this inside of standalone1 and run the same thing inside of standalone2 container and they should be connected?
y
yes. docker exec into the container and run the admin command.
a
I have tried that, but then when I move onto the next step on us-west: bin/pulsar-admin tenants create my-tenant \ --admin-roles my-admin-role \ --allowed-clusters us-west,us-east I get an error that says us-west does not exist The steps I followed: 1. I exec into container1 and created us-west and connected it to container2's url 2. I exec into container2 and created container us-east and connected it to container1's url
y
the default cluster name is “standalone”.
a
yeah theyre both called standalone but I can't run that command with the standalone name because it says "standalone already exists"
y
modify cluster name in conf/standalone.conf (us-west and us-east). then start over