-
Notifications
You must be signed in to change notification settings - Fork 621
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
Q: Excessive “consul: Health changed to #XXX” messages in fabio's log #205
Comments
Check if one or more of your services have flapping or lagging health checks.
|
@hynek I'm going to close this issue for now. Feel free to comment and I'll re-open it if necessary. |
yes thank you, I’m still investigating :-/ nothing is flapping but i'm not sure what a lagging health check would be? in any case this is probably not a fabio issue… happy holidays anyways. :) |
Hi, I've seen this exact same behaviour on my cluster. Just to throw some ideas, I've been debugging and found that is nomad the one causing this. The check that is performed on nomad is on /v1/agent/servers which outputs the servers of the cluster. The problem is that this array is not ordered and changes randomly (it's not random actually, but it is not guaranteed to be the same) on each request, so when there's more than one the check becomes the one causing the blocking query to end. I'll open an issue on nomad to see what they think about this. |
@jorgemarey I'll ping them as well. Thx. |
This PR should fix the issue: hashicorp/nomad#3214 |
Hi,
it feels awkward to ask here but it seems to be the right place…
I’ve got Fabio up and running without any issues except, that I’m getting very frequent log entries like this:
They usually come at least once per second. Is that normal or is something weird about our Consul/Vault/Nomad/Fabio setup?
TIA, Fabio’s great!
The text was updated successfully, but these errors were encountered: