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

add support to discover all marathon endpoints via DNS #16

Open
christianparpart opened this issue Jun 10, 2016 · 0 comments
Open

add support to discover all marathon endpoints via DNS #16

christianparpart opened this issue Jun 10, 2016 · 0 comments

Comments

@christianparpart
Copy link
Contributor

when you've a Marathon in a HA setup, you certainly expect one to go down, but what IP address to you connect to then when current one fails and remains down.

solution 1

discover all members via DNS SRV record (host and port), connect to any of them, use it; if one fails, try another one until it succeeds.

solution 2

allow passing multiple endpoints via command line parameter, and connect to one of them; if that fails, rotate through that list until one succeeds.

The endpoint list may contain DNS names to allow runtime relocation through DNS A record changes. (keeping the same port)

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

1 participant