[Cyberduck-trac] [Cyberduck] #10245: Configuration option for the part size when copying large objects
Cyberduck
trac at cyberduck.io
Thu Mar 1 21:39:57 UTC 2018
#10245: Configuration option for the part size when copying large objects
-------------------------+-------------------------
Reporter: jamshid | Owner: dkocher
Type: enhancement | Status: assigned
Priority: normal | Milestone: 7.0
Component: s3 | Version: 6.4.1
Severity: normal | Resolution:
Keywords: | Architecture: Intel
Platform: macOS 10.13 |
-------------------------+-------------------------
Description changed by dkocher:
Old description:
> Renaming of large (>5GB) objects works with S3 / S3-compatible since
> https://trac.cyberduck.io/ticket/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?
New description:
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?
--
--
Ticket URL: <https://trac.cyberduck.io/ticket/10245#comment:2>
Cyberduck <https://cyberduck.io>
Libre FTP, SFTP, WebDAV, S3 & OpenStack Swift browser for Mac and Windows
More information about the Cyberduck-trac
mailing list