Skip to content
This repository has been archived by the owner on Dec 20, 2018. It is now read-only.

bud on multiple boxes #72

Open
phillipp opened this issue Jul 15, 2015 · 2 comments
Open

bud on multiple boxes #72

phillipp opened this issue Jul 15, 2015 · 2 comments

Comments

@phillipp
Copy link
Contributor

We're going to deploy bud on multiple boxes in different DCs for DNS round-robin failover.

In the docs is a hint that ticket rotation will be a problem in this case (if I understand correctly). What is the setup for synchronized ticket rotation?

And: will there be any other problems?

@indutny
Copy link
Owner

indutny commented Jul 16, 2015

@phillipp yeah, the way it works right now is following:

  1. master spawns workers
  2. after some time master sends new ticket key to the workers using IPC

The way it should work on multi-box deployment is following:

  1. Something should spawn masters and connect to their ipc channels (using "master_ipc": true)
  2. Periodically send the same key to all masters in cluster
  3. Masters will send keys to workers

The problem is that there is no implementation for this multi-box thing yet.

@indutny
Copy link
Owner

indutny commented Jul 16, 2015

Guess, I can amend the node.js wrapper of bud, and make it expose this key rotation APIs using plain HTTP. But someone will need to start them, and to coordinate ticket rotation between multiple servers.

Does it make sense?

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants