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

configurable S3 PUT options #4526

Merged
merged 1 commit into from
Feb 19, 2024
Merged

Conversation

butonic
Copy link
Contributor

@butonic butonic commented Feb 19, 2024

The s3ng blobstore can now be configured with several options: s3.disable_content_sha254, s3.disable_multipart, s3.send_content_md5, s3.concurrent_stream_parts, s3.num_threads and s3.part_size. If unset we default to s3.send_content_md5: true, which was hardcoded before. We also default to s3.concurrent_stream_parts: true and s3.num_threads: 4 to allow concurrent uploads even when s3.send_content_md5 is set to true. When tweaking the uploads try setting s3.send_content_md5: false and s3.concurrent_stream_parts: false first, as this will try to concurrently stream an uploaded file to the s3 store without cutting it into parts first.

@butonic butonic self-assigned this Feb 19, 2024
@butonic butonic requested review from labkode, glpatcern and a team as code owners February 19, 2024 11:07
@butonic butonic force-pushed the configurable-s3-put-options branch from ecae2f9 to e48a559 Compare February 19, 2024 11:07
@butonic butonic force-pushed the configurable-s3-put-options branch from e48a559 to 02b2113 Compare February 19, 2024 13:56
Signed-off-by: Jörn Friedrich Dreyer <[email protected]>
@butonic butonic force-pushed the configurable-s3-put-options branch from 02b2113 to 1952b1d Compare February 19, 2024 13:58
@butonic butonic merged commit f95f5b4 into cs3org:edge Feb 19, 2024
9 checks passed
@butonic butonic deleted the configurable-s3-put-options branch February 19, 2024 14:19
@micbar micbar mentioned this pull request Feb 26, 2024
71 tasks
@fschade
Copy link
Contributor

fschade commented Mar 15, 2024

@kobergj we should check @butonic s comment above and try to find the sweet spot for our default conf, in my opinion the current setting is fine... but we have to understand every aspect of the options

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants