-
Notifications
You must be signed in to change notification settings - Fork 116
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
Support stale / consistent queries #110
Comments
https://www.consul.io/docs/agent/http.html says "most read query endpoints support specifying consistency". At the very least, this option would be useful for service and health API endpoints, because for service discovery being consistent is often less important than getting at least some results right. For more context, see https://stripe.com/blog/service-discovery-at-stripe. Consul v0.7.5 does not balk at those options being added to either health or catalog lookups. |
Any progress on that feature? Not being able to use stale makes every application based on diplomat unreliable when consul cluster does not have a leader. |
Please also consider 'leader' consistency mode => which forces basic consistency over discovery endpoints
|
Would you consider #165 ? Kind regards |
Now available with the changes in 2.1.0 |
https://www.consul.io/docs/agent/http.html under 'Consistency Modes'
The text was updated successfully, but these errors were encountered: