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

S3 primary storage: Object not found after writing when using an eventually consistent object storage provider. #25946

Closed
pierrejean-coudert opened this issue Mar 5, 2021 · 9 comments
Labels
0. Needs triage Pending check for reproducibility or if it fits our roadmap enhancement feature: object storage

Comments

@pierrejean-coudert
Copy link

pierrejean-coudert commented Mar 5, 2021

How to support this request?

  • Please use the 👍 reaction to show that you are also in favor of this feature - we are using this information to decide which features to include in upcoming Nextcloud versions.
  • Please don't comment if you have no relevant information to add

The S3 client behaviour generates an "Object not found after writing" exception using an eventually consistent object storage provider.

It currently checks immediately for the object existence after writing. This behaviour only works with a strongly consistent read-after-write object storage provider.

@sebastiansterk
Copy link
Member

@acsfer I'd rather say let's classify it as a bug because this leads into errors when uploading files. What do you think?

@szaimen
Copy link
Contributor

szaimen commented Jun 25, 2021

Is this Issue still valid in NC21.0.2? If not, please close this issue. Thanks! :)

@sebastiansterk
Copy link
Member

it's still valid.

@szaimen szaimen added 1. to develop Accepted and waiting to be taken care of feature: object storage and removed 0. Needs triage Pending check for reproducibility or if it fits our roadmap needs info labels Jun 25, 2021
@sebastiansterk
Copy link
Member

sebastiansterk commented Apr 24, 2022

This problem has been present for more than a year. Is there any priority for this problem? :(

@szaimen
Copy link
Contributor

szaimen commented Nov 26, 2022

Hi, please update to at least 23.0.12 and report back if it fixes the issue. Thank you!

@szaimen szaimen added needs info 0. Needs triage Pending check for reproducibility or if it fits our roadmap and removed 1. to develop Accepted and waiting to be taken care of labels Nov 26, 2022
@nextcloud-command

This comment has been minimized.

@nextcloud-command nextcloud-command added the stale Ticket or PR with no recent activity label Dec 31, 2022
@joshtrichards
Copy link
Member

@pierrejean-coudert What underlying S3 platform/provider were you experiencing this with?

@sebastiansterk
Copy link
Member

@pierrejean-coudert What underlying S3 platform/provider were you experiencing this with?

He uses exoscale's S3 compatible s3 storage: https://www.exoscale.com/object-storage/

@joshtrichards joshtrichards changed the title S3 primary storage: Object not found after writing S3 primary storage: Object not found after writing when using an eventually consistent object storage provider. Oct 6, 2023
@joshtrichards joshtrichards added enhancement and removed stale Ticket or PR with no recent activity 21-feedback labels Oct 6, 2023
@joshtrichards joshtrichards reopened this Oct 6, 2023
@joshtrichards
Copy link
Member

Supported added in #33458

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
0. Needs triage Pending check for reproducibility or if it fits our roadmap enhancement feature: object storage
Projects
None yet
Development

No branches or pull requests

6 participants