Dribble out bytes while handling long-running Complete Multipart Upload operations

Bug #1718811 reported by Tim Burke on 2017-09-22
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Swift3
Undecided
Unassigned

Bug Description

S3 docs say:

> Processing of a Complete Multipart Upload request could
> take several minutes to complete. After Amazon S3 begins
> processing the request, it sends an HTTP response header
> that specifies a 200 OK response. While processing is in
> progress, Amazon S3 periodically sends whitespace
> characters to keep the connection from timing out. Because
> a request could fail after the initial 200 OK response has
> been sent, it is important that you check the response
> body to determine whether the request succeeded.

We should do that, too! Swift already does something similar for bulk uploads and bulk deletes -- but not SLO. Swift3 may need to wait on SLO support, though :-/

Change abandoned by Tim Burke (<email address hidden>) on branch: master
Review: https://review.openstack.org/509321
Reason: Submitted against s3api as https://review.openstack.org/#/c/575818/

This issue was fixed in the openstack/swift 2.20.0 release.

The fix only handles the multi upload. What about multi delete? Multi delete with 1000 keys can take a long time, and we should send the whitespace char to keep the connection from timing out.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers