-
Notifications
You must be signed in to change notification settings - Fork 451
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
Question: Roles of nodes in memberlist #46
Comments
@diptanu You can! You want to use the |
Serf is confusingly both a CLI based agent, but also just a drop in library. Consul embeds the Serf library for example for all gossip related features. |
@armon Thanks a ton! This library is awesome :) Also, are you suggesting to use serf as a library instead of memberlist? Also, I need to put raft on top of serf like you guys do in Consul, however I need to do multiple smaller concensus groups within a cluster instead of a single concensus group. |
@diptanu Yeah the Serf library is both easier to use and has a ton more features. This library was meant to be almost purely an implementation of the SWIM algorithm, but many of the bells and whistles needed for the real world are in Serf. Sounds like you are working on something interesting, I'd love to learn more :) |
Given you recommend using Serf as a library, are there any docs on doing that? I've been looking at the Consul code to see how this is done, and that gets me pretty far, but it's a lot of context switching. Thanks for both of these things! |
@kyleterry How about opening an issue with the Serf project/repo instead? @kyleterry @armon I suggest this issue can be closed. |
Just curious, why does serf depend on memberlist? |
Hi @armon and @mitchellh ,
Do you think it would be possible to designate role or additional metadata regarding a node when it joins a cluster? I understand that it's currently not possible but would be interested in a PR which would allow a user to configure the role of a node and query memberlist for nodes with specific metadata?
We are currently using the name field and adding more information to the name and parse the names to decipher the roles of various nodes in a cluster.
The text was updated successfully, but these errors were encountered: