Fix: Lock can be acquired after lease duration if the current owner has been terminated unexpectedly when using skipBlockingWait=true

awslabs / amazon-dynamodb-lock-client

The AmazonDynamoDBLockClient is a general purpose distributed locking library built on top of DynamoDB. It supports both coarse-grained and fine-grained locking.

Other

472 stars 85 forks source link

Fix: Lock can be acquired after lease duration if the current owner has been terminated unexpectedly when using skipBlockingWait=true #91

Open shetsa-amzn opened 1 year ago

shetsa-amzn commented 1 year ago

Issue #, if available: https://github.com/awslabs/amazon-dynamodb-lock-client/issues/44

Description of changes: The change in this PR after resolving few conflicts

https://github.com/awslabs/amazon-dynamodb-lock-client/pull/79

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

rahulvishwanatham commented 10 months ago

I am facing the same issue with 1.2.0 version, is this going to be merged or any other solution to this? A lock is stale in my DDB and no other instance is able to acquire the lock. I am setting withShouldSkipBlockingWait.