[
https://issues.apache.org/jira/browse/CLOUDSTACK-4816?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13814829#comment-13814829
]
Pavan Kumar Bandarupally commented on CLOUDSTACK-4816:
------------------------------------------------------
A new global setting s3.singleupload.max.size is added, which determines the
size (cap 5GB) below which single part is to be used for uploading.
> provide configurable option to choose single vs multipart upload to S3 object
> storage
> --------------------------------------------------------------------------------------
>
> Key: CLOUDSTACK-4816
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4816
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Storage Controller
> Affects Versions: 4.2.0
> Reporter: Min Chen
> Assignee: Min Chen
> Priority: Critical
> Fix For: 4.2.1
>
>
> In 4.2, we only supports multipart upload for registering templates and
> uploading volumes to object storage in secondary storage. The value of
> multi-part is for network failure and throughput when you are going to a
> remote storage. But with local storage (local to the DC) customers may prefer
> single upload. Also, for templates you know the full size of the object
> upfront and don't really need a multipart upload.
> Some object storage vendors may prefer that this can be configured.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
