libcloud-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tomaz Muraus (JIRA)" <>
Subject [jira] [Commented] (LIBCLOUD-378) S3 uploads fail on small iterators
Date Tue, 03 Sep 2013 09:47:53 GMT


Tomaz Muraus commented on LIBCLOUD-378:

I just checked the docs ( and it

Part size	5 MB to 5 GB, last part can be < 5 MB

I would image that it should work if there is only one part and it's smaller than 5 MB, because
first part=last part.

In any case it would still be good to test that. 

[~mahendra.m] Can you please test the thing I've mentioned above (uploading a small file which
results in a single chuck)?

If it works, please update the CHANGES file and feel free to merge this patch into trunk.

> S3 uploads fail on small iterators
> ----------------------------------
>                 Key: LIBCLOUD-378
>                 URL:
>             Project: Libcloud
>          Issue Type: Bug
>          Components: Storage
>            Reporter: John Carr
>         Attachments: LIBCLOUD-378.diff
> I wrote a small script that uploaded the output of a buildbot job and then updated an
XML file. The large binary blob worked fine. However the XML file failed.
> I was using the driver.upload_object_via_stream(iterator=StringIO.StringIO(somexml))
style as in the docs.
> Looking at the LIBCLOUD_DEBUG output the driver was using the S3 multi-part upload API
and making a new "part" for each line - so every 7 bytes or so - but the minimum size for
a part upload was 5mb.
> (I don't know if the first part is allowed to be less than 5mb if the entire upload is
less than 5mb).
> I am working around this by forcing multi-part uploads off.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message