-
Notifications
You must be signed in to change notification settings - Fork 84
Handle pubsub messages in multi instance scenario #105
Comments
Subscriptions and pubsub router will be run by skygear server in leader mode. Cloudcode should connect to leader by configuring the PUBSUB_URL environment variable. refs SkygearIO#105
Subscriptions and pubsub router will be run by skygear server in leader mode. Cloudcode should connect to leader by configuring the PUBSUB_URL environment variable. refs SkygearIO#105
Subscriptions and pubsub router will be run by skygear server in leader mode. Cloudcode should connect to leader by configuring the PUBSUB_URL environment variable. refs SkygearIO#105
Subscriptions and pubsub router will be run by skygear server in leader mode. Cloudcode should connect to leader by configuring the PUBSUB_URL environment variable. refs SkygearIO#105
Subscriptions and pubsub router will be run by skygear server in leader mode. Cloudcode should connect to leader by configuring the PUBSUB_URL environment variable. refs SkygearIO#105
Subscriptions and pubsub router will be run by skygear server in leader mode. Cloudcode should connect to leader by configuring the PUBSUB_URL environment variable. refs SkygearIO#105
Subscriptions and pubsub router will be run by skygear server in leader mode. Cloudcode should connect to leader by configuring the PUBSUB_URL environment variable. refs SkygearIO#105
Revisiting this issue, in #127 we added the configuration on slave and disabled the whole pubsub and cron feature at slave mode. So the do @cheungpat think following two feature are still meaningful to implement
Or better tol provide a deployment example on how to route the traffic correctly using the program like nginx? |
@rickmak Thanks for bringing it to my attention. I think the feature is complete in skygear-server and py-skygear to support multiple instances. Agree that we should have deployment example. Where to put it?
Cloudcode generated messages are forwarded to leader using PUBSUB_URL. In slave mode, skygear-server does not generate notifications for subscriptions
This is just a reminder not to cause infinite loop forwarding notifications among multiple instances. Since only the leader will act as pubsub hub. This is a non-issue. |
Let put the example here: https://github.com/skygear-demo/multiple-server |
To fix #91, we have to handle how pubsub messages are routed to the client. To solve this, the leader instance will be asked to keep pubsub connections for all clients. Pubsub generated from other instances should forward pubsub messages to the leader instance.
Tasks:
The text was updated successfully, but these errors were encountered: