search

nextcloud / server

☁️ Nextcloud server, a safe home for all your data
https://nextcloud.com
GNU Affero General Public License v3.0
26.71k stars 4k forks source link

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

Open pierrejean-coudert opened 3 years ago

pierrejean-coudert commented 3 years ago

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 commented 3 years ago

@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 commented 3 years ago

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

sebastiansterk commented 3 years ago

it's still valid.

sebastiansterk commented 2 years ago

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

szaimen commented 1 year ago

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

nextcloud-command commented 1 year ago

This issue has been automatically marked as stale because it has not had recent activity and seems to be missing some essential information. It will be closed if no further activity occurs. Thank you for your contributions.

joshtrichards commented 11 months ago

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

sebastiansterk commented 11 months ago

@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/