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

Concurrency with azmi #229

Open
maksiml2014 opened this issue Jan 12, 2021 · 1 comment
Open

Concurrency with azmi #229

maksiml2014 opened this issue Jan 12, 2021 · 1 comment
Assignees
Labels
bug Something isn't working

Comments

@maksiml2014
Copy link

azmi getblob/setblob shoud be an ataomic transaction.
If setblob fails halfway through, then the process should roll back and an old version of file should persist.
If getblob is called on a file that is currently being written by setblbob, then either getblob should wait or download the old version of the file. Either way, the behaviour shoud be documented in azmi.

@MangyCoyote MangyCoyote self-assigned this Jan 12, 2021
@MangyCoyote MangyCoyote added the bug Something isn't working label Jan 12, 2021
@MangyCoyote
Copy link
Collaborator

Either blob lease or http header ETag should fix it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants