-
Notifications
You must be signed in to change notification settings - Fork 98
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Connecting multiple swarm hosts (backend) #44
Comments
Hi! That part of the code is lagging behind and I don't expect it to work as of now. Ironically, a consistent hashing server cluster was our first demo back in 2013. |
Thanks for your response, I will try digging further to see if I can solve this. |
Yep, 0.4 puts an accent on server-side stuff. |
Is that feature done for 0.4 ? |
Consistent hashing server rings, ETA is early-December. |
Hi!
I'm trying to set up a swarm cluster on the backend but am having a couple of issues. Reading the code, in Pipe.js it says that a pipe is a channel to a remote swarm host. This works great when the connection is from client -> server, but not so much when doing server -> server. I am able to connect servers to each other but there does not appear to be any replication going on between different instances.
My issue is that we need more then one machine on the back end and since users that share models could be connected to different physical hosts we need a way to ensure that each server stays up to date and that data is replicated correctly.
Is there a way to accomplish this today?
The text was updated successfully, but these errors were encountered: