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

Host down #1

Open
danilobuerger opened this issue Nov 9, 2015 · 4 comments
Open

Host down #1

danilobuerger opened this issue Nov 9, 2015 · 4 comments

Comments

@danilobuerger
Copy link

Is there any solution in this library on how to handle if a host selected by the load balancer is down? Or would one build that on top? Or would one need a custom strategy for that?

@benschw
Copy link
Owner

benschw commented Nov 16, 2015

The way I've used it, is in conjunction with a service discovery system (like consul) that is in charge of keeping the dns entries up to date. There is still the ttl window when this data may be stale, but the library does not attempt to validate entries or perform retries (however, since each request to the library hits the DNS server, you could implement your own retry and just query for an address again).

@benschw
Copy link
Owner

benschw commented Nov 16, 2015

(let me know if I'm misunderstanding your question)

@danilobuerger
Copy link
Author

So sorting out hosts that are down (during the ttl window) is out of scope for this library?

@benschw
Copy link
Owner

benschw commented Nov 17, 2015

Yeah. I think any kind of test would just shrink the ttl, so a real solution would involve retrys similar to how netflix's ribbon does things. This would be interesting to solve but is currently out of scope.

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