Skip to content

Commit

Permalink
Removed lockAtLeastFor section
Browse files Browse the repository at this point in the history
  • Loading branch information
@Saphri
Saphri committed Nov 19, 2024
1 parent 163ef48 commit 0614d75
Showing 1 changed file with 0 additions and 7 deletions.
7 changes: 0 additions & 7 deletions README.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -905,13 +905,6 @@ But instead you can do:

Buckets are auto created with fixed TTL, but never deleted. So any timing changes will require manual deletion of the bucket. NatsJetStreamLockProvider will trigger log warning if this mismatch is detected.

Support for LockAtLeastFor is the following due to bucket TTL limitation.
Example with 400ms lockAtLeastFor, and 800ms lockAtMost.
Call unlock before 400ms lockAtLeastFor is up. Lock will stay for AtMostFor timing (800ms)
Call unlock after 400ms lockAtLeastFor was up. Lock will be deleted asap.

NatsJetStreamLockProvider will trigger log warning if this setting is used.

NATS 2.11 should make it possible to define TTL on key level when released... so fingers crossed :D

Import the project
Expand Down

0 comments on commit 0614d75

Please sign in to comment.