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

Value of etcd instance lock could be more informative #321

Open
przemyslaw-dobrowolski-cl opened this issue Oct 18, 2016 · 0 comments
Open

Comments

@przemyslaw-dobrowolski-cl
Copy link
Contributor

During the process of master server selection, each gohan server performs a CAS operation in etcd in order to lock itself as a leader. The key is a constant path for all servers but the value is composed of the server host name and an randomly chosen UUID. This could be improved for the purpose of tracking down which Gohan server is the current leader. Using an IP address instead of the host name (or using both of these) would be more informative as the hostname does not need to be unique nor informative nor easy to dns-reverse in a local network.

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

No branches or pull requests

2 participants