SCC Guide - Unable or unsure to run on multiple machines #519
Comments
|
Ah I found that by stopping the broker server on local has allowed client messages to connect to each other. So I only need one machine to run state and broker services, while other machines simply run the client servers? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This is wonderful work and I'm very grateful to find this repo. I'm having difficulty understanding how to scale to multiple networks following the SCC guide and also confused on the recommended architecture. The main issue is clients on separate servers are not finding messages from each other.
On a gcloud instance, i start the state (node server.js), broker( SCC_STATE_SERVER_HOST='[google given ip]' SCC_BROKER_SERVER_PORT='8888' node server ), and ( SCC_STATE_SERVER_HOST='[google given ip]' SOCKETCLUSTER_PORT='8000' node server ) client servers. Everything works and I can access the google given ip from anywhere.
On my localhost I start broker and client servers with the same commands with the google ips. The state server registers the brokers and workers on both machines:
The client server on the google ip reacts to emitting a message from the browser connecting to the google IP but the local client server does not react to emitting a message from the localhost browser connection. Both client servers are throwing:
Am I missing something? I made one change to the broker server to use 'ws' since 'sc-uws' was giving compilation errors. Thanks!
The text was updated successfully, but these errors were encountered: