summaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorGravatar Joey Hess <joeyh@joeyh.name>2015-06-15 15:00:02 -0400
committerGravatar Joey Hess <joeyh@joeyh.name>2015-06-15 15:00:02 -0400
commit80e608341e2e39f560711f7c9410c619d8f6c1b6 (patch)
treeb15d898008ba9e3d3a9c4b27868a993284a63f74 /doc
parentd45f7b5404bdd2d9204836e9305ead9efb3711fc (diff)
followup
Diffstat (limited to 'doc')
-rw-r--r--doc/bugs/s3_InternalIOException__63__/comment_1_42bd2d1e364203f1b34efcc34ac795b8._comment14
1 files changed, 14 insertions, 0 deletions
diff --git a/doc/bugs/s3_InternalIOException__63__/comment_1_42bd2d1e364203f1b34efcc34ac795b8._comment b/doc/bugs/s3_InternalIOException__63__/comment_1_42bd2d1e364203f1b34efcc34ac795b8._comment
new file mode 100644
index 000000000..544c8998f
--- /dev/null
+++ b/doc/bugs/s3_InternalIOException__63__/comment_1_42bd2d1e364203f1b34efcc34ac795b8._comment
@@ -0,0 +1,14 @@
+[[!comment format=mdwn
+ username="joey"
+ subject="""comment 1"""
+ date="2015-06-15T18:57:07Z"
+ content="""
+Are you sure that it was subsequent transfers of other keys that failed,
+and not subsequent transfers of chunks of the same key?
+
+The latter seems more likely. There is a cached connection to S3 that is
+reused when uploading chunks of a key. But, each transfer of a key
+currently runs using its own individual connection. Difficulties with
+connections that close or are left running too long are why the S3 remote
+doesn't yet reuse connections.
+"""]]