-
Notifications
You must be signed in to change notification settings - Fork 34
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
Blobstore can throw FileAlreadyExistsException #10447
Comments
closed by mistake |
rymsha
added a commit
that referenced
this issue
Dec 23, 2024
rymsha
added a commit
that referenced
this issue
Dec 23, 2024
rymsha
added a commit
that referenced
this issue
Dec 23, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
With a chance of nodes to be created with exactly the same blob (and it does not already exist) - there is a race condition
one of the nodes won't be created.
There is another race: when one thread creates blob - and writes data to it, while another sees the blob, and tries to read contents of it, there is a chance that contents are not yet fully written - because file writes are not atomic and we don't use write-then-copy approach in FileBlobStore. This leads to broken blobs cached.
The text was updated successfully, but these errors were encountered: