Skip to content

Disallow stale reads for Consul CAS #3259

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

Merged
merged 2 commits into from
Oct 6, 2020
Merged

Disallow stale reads for Consul CAS #3259

merged 2 commits into from
Oct 6, 2020

Conversation

bboreham
Copy link
Contributor

@bboreham bboreham commented Oct 1, 2020

In order for the CAS to succeed, we need to have up-to-date data to compare against, so it doesn't make sense to allow stale reads. More info: https://www.consul.io/api-docs/features/consistency

The default for -consul.consistent-reads was changed to false in #2344.

Checklist

  • NA Tests updated
  • NA Documentation added
  • CHANGELOG.md updated

In order for the CAS to succeed, we need to have up-to-date data to
compare against, so it doesn't make sense to allow stale reads.

More info: https://www.consul.io/api-docs/features/consistency

Signed-off-by: Bryan Boreham <[email protected]>
Copy link
Contributor

@pstibrany pstibrany left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Makes sense, good find!

Copy link
Contributor

@pracucci pracucci left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM!

@pracucci pracucci merged commit 844759a into master Oct 6, 2020
@bboreham bboreham deleted the consul-consistent-cas branch October 6, 2020 15:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants