diff options
| author |  Joey Hess <joey@kitenet.net> | 2014-11-03 15:53:22 -0400 |
|---|---|---|
| committer | Joey Hess <joey@kitenet.net> | 2014-11-03 16:04:55 -0400 |
| commit | b69362e972190668a0742059f0798d2ce00f15c6 (patch) | |
| tree | 9d3a8c88fdd885141f423be00978532e5faa9ddd /doc/bugs/S3_upload_not_using_multipart.mdwn | |
| parent | 9d7f923e5b3466a8fe3b34781483cb6a115fe5fc (diff) | |
finish multipart support using unreleased update to aws lib to yield etags
Untested and not even compiled yet.
Testing should include checks that file content streams through without
buffering in memory.
Note that CL.consume causes all the etags to be buffered in memory.
This is probably nearly unavoidable, since a request has to be constructed
that contains the list of etags in its body. (While it might be possible to
stream generation of the body, that would entail making a http request that
dribbles out parts of the body as the multipart uploads complete, which is
not likely to work well..
To limit this being a problem, it's best for partsize to be set to some
suitably large value, like 1gb. Then a full terabyte file will need only
1024 etags to be stored, which will probably use around 1 mb of memory.
Diffstat (limited to 'doc/bugs/S3_upload_not_using_multipart.mdwn')
| -rw-r--r-- | doc/bugs/S3_upload_not_using_multipart.mdwn | 8 |
1 files changed, 8 insertions, 0 deletions
diff --git a/doc/bugs/S3_upload_not_using_multipart.mdwn b/doc/bugs/S3_upload_not_using_multipart.mdwn index 5e5d97c6a..cd40e9d2b 100644 --- a/doc/bugs/S3_upload_not_using_multipart.mdwn +++ b/doc/bugs/S3_upload_not_using_multipart.mdwn @@ -52,3 +52,11 @@ Please provide any additional information below. upgrade supported from repository versions: 0 1 2 [[!tag confirmed]] + +> [[fixed|done]] This is now supported, when git-annex is built with a new +> enough version of the aws library. You need to configure the remote to +> use an appropriate value for multipart, eg: +> +> git annex enableremote cloud multipart=1GiB +> +> --[[Joey]] |