Closed chris-ryan-square closed 1 year ago
I could be wrong, but the addition of the LOOKUP_TIME attribute means that this would be a great solution for:
https://github.com/awslabs/amazon-dynamodb-lock-client/issues/34
I wonder if it would be even better to store an 'expiration time' instead, as that could be functionally the same but also allow for easy integration with the TTL feature:
https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/TTL.html
I agree that we should abandon this proposed change for #88 after it is revised.
No longer required
Issue #, if available: 44
Description of changes:
This solves the problem with the issue raised, allowing skipBlockingWait flag to be used safely. It tracks the "lookupTime" for the lock to handle if another client that has the lock has been terminated unexpectedly - and therefore can't update the lock itself.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.