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

Initial suggestion for Global locking for Timed Services for v9 #3093

Merged
merged 1 commit into from
May 16, 2024

Conversation

preardon
Copy link
Member

issue #3075

Copy link
Member

@iancooper iancooper left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

With the Azure Storage Lock (showing my ignorance of Azure here) how do we ensure that if you crash without doing a Release, someone else can grab the lock?

@preardon
Copy link
Member Author

preardon commented May 16, 2024

@iancooper The way this works is using something called a Blob Lease which can be between 15 and 60 seconds, after that the lease expires. so if the process was to crash (or unfortuneatly take over the specified lock time) the lease would expire and would be available for locking again.

There is a setting called LeaseValidity (will get around to the documentation afer we've agreed on approach) that is defaulted to 1 minute

@preardon preardon force-pushed the distributedLock9x branch from 6b71011 to 1ed7fe8 Compare May 16, 2024 18:30
@preardon preardon merged commit 52bfdca into BrighterCommand:release/9X May 16, 2024
4 checks passed
@preardon preardon deleted the distributedLock9x branch May 16, 2024 18:33
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.

2 participants