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

discovery and the use of "priority" #204

Closed
nuttysquirrel opened this issue Mar 8, 2019 · 2 comments
Closed

discovery and the use of "priority" #204

nuttysquirrel opened this issue Mar 8, 2019 · 2 comments
Assignees
Labels
Milestone

Comments

@nuttysquirrel
Copy link

I'm using gobetween as a front end for an anycast dns setup.
I wanted to be able to say "use 1.1.1.1 always, unless healthcheck marks it down - then use 2.2.2.2"
Current setup runs a dynamic discovery every 10 minutes, with a healthcheck every minute....
Reading the documentation on github a number of times didn't make it clear to me how to do the 'absolute priority' situation I described, so I guessed maybe returning 'priority' in discovery...
So, the discovery mechanism returns;
1.1.1.1 priority=1
2.2.2.2 priorty=2
However, gobetween seems to ignore the priority and uses both of them.
sorry if this is obviousky crazy - 'go' is new to me and i'm still going through the source to try and understand it.

@nuttysquirrel
Copy link
Author

nuttysquirrel commented Mar 25, 2019

made a "priority" balancer and put it here:
https://github.com/nuttysquirrel/gobetween/tree/master

@yyyar
Copy link
Owner

yyyar commented Jun 22, 2019

Merged to master, will be available in next release.

@yyyar yyyar closed this as completed Jun 22, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants