[Cyberduck-trac] [Cyberduck] #10245: Configuration option for the part size when copying large S3 objects

Cyberduck trac at cyberduck.io
Tue Feb 27 00:43:49 UTC 2018


#10245: Configuration option for the part size when copying large S3 objects
------------------------+-------------------------
    Reporter:  jamshid  |      Owner:
        Type:  defect   |     Status:  new
    Priority:  normal   |  Milestone:
   Component:  s3       |    Version:  6.4.1
    Severity:  normal   |   Keywords:
Architecture:  Intel    |   Platform:  macOS 10.13
------------------------+-------------------------
 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?

--
Ticket URL: <https://trac.cyberduck.io/ticket/10245>
Cyberduck <https://cyberduck.io>
Libre FTP, SFTP, WebDAV, S3 & OpenStack Swift browser for Mac and Windows


More information about the Cyberduck-trac mailing list