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

Configuration option for the part size when copying large objects #10245

Closed
cyberduck opened this issue Feb 27, 2018 · 2 comments
Closed

Configuration option for the part size when copying large objects #10245

cyberduck opened this issue Feb 27, 2018 · 2 comments

Comments

@cyberduck
Copy link
Collaborator

@cyberduck cyberduck commented Feb 27, 2018

4e36ae0 created the issue

Renaming of large (>5GB) objects works with S3 / S3-compatible since #9983 was implemented to use multipart, where each part is a server-side copy of the original stream.

The problem is that this does a 5GB part copy. Since that's such a large copy that can timeout the request. I'm getting that with an S3-compatible system.

Is there any way you can lower that part size, or make it configurable?

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Mar 1, 2018

@dkocher commented

You can set the hidden configuration option s3.copy.multipart.size. Refer to Hidden configuration options.

Loading

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Mar 2, 2018

@dkocher commented

In a589758.

Loading

@cyberduck cyberduck closed this Mar 2, 2018
@iterate-ch iterate-ch locked as resolved and limited conversation to collaborators Nov 26, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants