Péter Pallinger (Jun 26 2026 at 08:16): Péter Pallinger (Jun 26 2026 at 08:16):We recently (few months ago) upgraded to 6.9, and just noticed that dataverse does not use the multipart method for uploading to the ceph-based s3 storage we have, thus failing to upload any file larger than 4GiB. I tried setting dataverse.files.<id>.chunked-encoding to both true and false, but neither works. I managed to find an old test server that contained a 6.1 instance, and it correctly sends the upload in many parts with uploadId and partNumber parameters.
Is there an option to get the old behaviour back? Or are there s3 profile options that I can set in the .aws/config file?
I am currently trying to find when the error occurred, but is is quite slow, so any help is appreciated!
Péter Pallinger (Jun 26 2026 at 08:18):Before you ask: direct upload is not an option, at least in the short-term.
Péter Pallinger (Jun 26 2026 at 08:22):Sorry, I did not find #troubleshooting > ✔ Multipart upload broken after v6.7 for S3 compatible st... , the search function does not seem to be very good... I will try to use the patch linked there.
Péter Pallinger (Jun 26 2026 at 09:55):I cherry-picked the relevant commit (https://github.com/IQSS/dataverse/pull/12358/changes/e8128c3361c02a9bf127d45ca7b835eeaf8230cd), it seems to work.
Notification Bot (Jun 26 2026 at 09:55):Péter Pallinger has marked this topic as resolved.
Philip Durbin 🚀 (Jul 01 2026 at 14:05):No worries! This bug is listed first in the 6.11 release notes. I'm glad a fix will be going out to everyone soon.
Last updated: Aug 18 2026 at 08:27 UTC