issues
search
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
490
stars
92
forks
source link
issues
Newest
Newest
Most commented
Recently updated
Oldest
Least commented
Least recently updated
Fetch lock item from `notMyLocks` only once
#110
ThePumpingLemma
opened
1 month ago
0
amazon-dynamodb-lock-client for AWS SDK v2
#109
anasokan
opened
2 months ago
1
Update additional attributes on lock release
#108
nathanallen-toast
opened
3 months ago
1
Versions 1.1 and >1.1 use the same package name, but use different AWS SDKs.
#107
adstalla
opened
6 months ago
0
Updating the latest version to 1.3
#106
shetsa-amzn
closed
7 months ago
0
Upgrade docker plugin
#105
shetsa-amzn
closed
7 months ago
0
Fix test coverage and update maven version
#104
ethkatnic
closed
7 months ago
0
Why multi-threading is blocking with configuing withShouldSkipBlockingWait = True
#103
Kiollpt
opened
8 months ago
1
Update README.md for LockCurrentlyUnavailableException
#102
moshegood
opened
1 year ago
0
Separate blocking and non-blocking methods instead of using skipBlockingWait
#101
lcabancla
closed
1 year ago
0
Synchonized Migration and Thread Creation Overrides (Support for Virtual Threads)
#100
murbot
opened
1 year ago
1
Fix: ShouldSkipBlockingWait should still acquire a dead lock if tried for longer than TTL
#99
moshegood
closed
7 months ago
0
Is this project dead?
#98
cin
opened
1 year ago
1
Avoid `synchronized` during blocking operations (loom friendliness)
#97
ravi-signal
opened
1 year ago
0
Upgrade aws skd version
#96
MjdBh
opened
1 year ago
0
Failed to run demo code
#95
user1689
opened
1 year ago
1
Potential Bug - Client should reset leaseDuration waiting time when recordVersionNumber noticed to change
#94
basilmusa
opened
1 year ago
0
withShouldSkipBlockingWait will always fail to acquire lock if already exists and expired
#93
cristianocca
opened
1 year ago
8
[Feature Request] Soft Unlock
#92
qvissak
opened
1 year ago
0
Fix: Lock can be acquired after lease duration if the current owner has been terminated unexpectedly when using skipBlockingWait=true
#91
shetsa-amzn
closed
7 months ago
1
chore: ✏️ fix typos
#90
jbleduigou
opened
2 years ago
3
Table cloudformation template
#89
steve-thousand
opened
2 years ago
0
Add a withClockSkewUpperBound option when acquiring a lock
#88
tso
opened
2 years ago
3
Removing Warning / Clarification from README.md since new version(1.2…
#87
shetsa-amzn
closed
2 years ago
0
Upgrade AWS SDK - 2.20.8 and DynamoDBLocal - 1.21.0
#86
shetsa-amzn
closed
2 years ago
0
amazon-dynamodb-lock-client as singleton
#85
gianluigiruggeri
opened
2 years ago
0
Release AWS SDKv2
#84
dmytrodanilenkov
closed
2 years ago
1
Change License to ASLv2 or MIT
#83
frotsch
opened
2 years ago
1
Interest in a TypeScript port?
#82
jcrites
opened
2 years ago
1
feat: update dependencies
#81
tvcsantos
opened
2 years ago
1
Is it possible to migrate this set of logic to a relational database, such as MySQL
#80
EternalSaul
opened
2 years ago
0
Fix: Lock can be acquired after lease duration if the current owner has been terminated unexpectedly when using skipBlockingWait=true
#79
chris-ryan-square
closed
1 year ago
3
Service: AmazonDynamoDBv2; Status Code: 400; Error Code: AccessDeniedException
#78
alecmedvedev
opened
2 years ago
0
Documentation on inter-region locking
#77
pratyoosh
opened
3 years ago
0
Any port on the horizon to Python/Javascript?
#76
convexset
opened
3 years ago
0
Upgrade to JDK17+
#75
chris-ryan-square
closed
2 years ago
1
Updating README for clarification
#74
justinwlin-amazon
closed
3 years ago
0
jenkins files added.
#73
bsugarjav
closed
3 years ago
0
Bump log4j-core from 2.17.0 to 2.17.1
#72
dependabot[bot]
closed
3 years ago
0
Bump log4j-core from 2.16.0 to 2.17.0
#71
dependabot[bot]
closed
3 years ago
0
log4j-core bug fix
#70
justinwlin-amazon
closed
3 years ago
0
Bump log4j-core from 2.14.1 to 2.15.0
#69
dependabot[bot]
closed
3 years ago
1
Getting this exception while app initialisation. Is this some known issue?
#68
isha01
opened
3 years ago
1
can client.acquireLock callback be made asynchronous?
#67
mrshappy0
opened
3 years ago
0
Will the latest release be pushed to Maven?
#66
bengaudiosi-toast
closed
2 years ago
1
Update pom.xml to work with new mvn deployment loop
#65
justinwlin-amazon
closed
3 years ago
0
Fixing commenting curly braces to allow for JavaDoc to compile codebase
#64
justinwlin-amazon
closed
3 years ago
1
Heartbeat thread working with lambda
#63
nitika-bansal
opened
3 years ago
1
Document limitations of locks issued
#62
tobyhei
opened
3 years ago
5
Can we push the 1.2.0 release to the maven repo?
#61
zhedoubushishi
closed
2 years ago
5
Next