Skip to content
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

dynamic node list #4

Open
benoitc opened this issue Aug 30, 2011 · 1 comment
Open

dynamic node list #4

benoitc opened this issue Aug 30, 2011 · 1 comment

Comments

@benoitc
Copy link

benoitc commented Aug 30, 2011

Is there a way to add dynamically a nodes to the list of potential leaders?

@archaelus
Copy link
Contributor

Right now? No.

The Async Bully algorithm given by Stoller doesn't contain any mechanism for updating the set of peers and quite a bit of the algorithm seems dependent on the set being identical on all nodes. However, operationally it's a pain not to have this capability, so I'll have a think about it.

Currently messages are tagged with the election_id, gl_async_bully name and a few other things to make sure that only processes with the right configuration participate in the protocol. Perhaps we could add a checksum over the whole configuration (service name, peer set, election_id) to the messages instead which will prevent differently configured nodes from interfering with eachother. We could then add a broadcast message from the leader to change the configuration. At worst, if the update message gets lost, then some nodes will form effectively disconnected subsets (and elect their own leaders), but different subsets won't interfere with each other as they'll ignore eachother's messages.

Anyone else have ideas on how to solve this?

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

No branches or pull requests

2 participants