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

Spurious update fix #247

Merged
merged 9 commits into from Oct 25, 2017
Merged

Spurious update fix #247

merged 9 commits into from Oct 25, 2017

Conversation

sahilpalvia
Copy link
Contributor

Issues addressed in this PR

Sam Day and others added 8 commits August 14, 2017 17:08
If the request to conditionally update a lease counter in DynamoDB fails, it's
considered a failure to renew the lease. This is a good thing, except if the
request failure was just because of connectivity problems. In this case the
counter *did* update in DynamoDB, but the Dynamo client retries the request
which then fails the update condition (since the lease counter no longer
matches expected value).

To handle this gracefully we opt to get the lease record from Dynamo and
examine the lease owner and counter. If it matches what we were expecting,
then we consider renewal a success.
@pfifer pfifer added this to the v1.8.8 milestone Oct 25, 2017
@pfifer pfifer merged commit 7032ea6 into awslabs:master Oct 25, 2017
@sahilpalvia sahilpalvia deleted the spurious-update-fix branch October 25, 2017 23:10
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

Successfully merging this pull request may close these issues.

None yet

2 participants