[Cyberduck-trac] [Cyberduck] #9131: Arbitrary Swift Object Size Limit 100GB

Cyberduck trac at trac.cyberduck.io
Tue Nov 24 05:10:33 UTC 2015

#9131: Arbitrary Swift Object Size Limit 100GB
    Reporter:  jmamma     |      Owner:  dkocher
        Type:  defect     |     Status:  new
    Priority:  high       |  Milestone:
   Component:  openstack  |    Version:  4.7.3
    Severity:  critical   |   Keywords:
Architecture:             |   Platform:
 '''Cyberduck has an arbitrary 100GB Object Size limit.'''

 '''Observed Behavior:'''

 When uploading an object larger than 100GB to Swift Storage, all segments
 will be transferred but the complete operation will fail at 100%.

 "Request Entity Too Large. 413 Request Entity Too Large"

 The Object manifest is not created.

 '''It appears to be related to the design decision below:'''



 "We changed the part size for multipart uploads to 10MB in r14143 to allow
 multipart uploads up to 100GB in total size due to the maximum number of
 parts restriction of 10'000 by S3. Please try with the latest ​snapshot
 build available and reopen this ticket if you are still having this


 From my understanding you're failing at objects greater than 100GB to
 prevent more than 10,000 segment being created (an S3 limit).
 OpenStack Swift does not have a hard upper limit on the total number of
 objects stored in a container.


 I've been able to override the default user setting:
 openstack.upload.largeobject.size to 1,048,576,000 (1GB)
 which is approximately the default segment size used by the Python Swift
 Client and increasing the Cyberduck object size limit to 1TB.

 Manually editing the Cyberduck user.config xml file is a less than
 desirable solution for our users, who routinely upload 100GB or larger

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

More information about the Cyberduck-trac mailing list