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

Socket connection timeout #36

Open
missinglink opened this issue May 22, 2019 · 1 comment
Open

Socket connection timeout #36

missinglink opened this issue May 22, 2019 · 1 comment

Comments

@missinglink
Copy link
Member

It would be great if the requests would timeout instantly in the case where the socket connection was not possible, such as when the port is closed or the host is down.

I had a quick look at the docs for superagent, and while they have two different timeout settings, neither of them seems to cover this case.

It would allow us to timeout much faster when a service was configured but unavailable due to misconfiguration or outage.

related: pelias-deprecated/kubernetes#81

@orangejulius
Copy link
Member

Yeah this is interesting, this might be something that is only a problem for us with K8S. Worst case, we might want to warn people that if they are not going to use all pelias services, they should ensure that the unused services are disabled in pelias.json, for example by using enabled: false in the Helm config.

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