[tahoe-lafs-trac-stream] [Tahoe-LAFS] #1678: S3 backend: either handle or avoid truncated get_bucket responses

[Tahoe-LAFS]

#1678: S3 backend: either handle or avoid truncated get_bucket responses
------------------------------+----------------------------
     Reporter:  davidsarah    |      Owner:  davidsarah
         Type:  defect        |     Status:  closed
     Priority:  critical      |  Milestone:  1.12.0
    Component:  code-storage  |    Version:  1.9.0-s3branch
   Resolution:  fixed         |   Keywords:  s3-backend 410
Launchpad Bug:                |
------------------------------+----------------------------
Changes (by daira):

 * milestone:  soon => 1.12.0


Old description:

> The GET Bucket AWS call may return a truncated response, by default after
> 1000 objects
> [http://docs.amazonwebservices.com/AmazonS3/latest/API/RESTBucketGET.html
> (doc)]. Currently we don't take that into account (actually I forgot that
> we didn't :-( ), which might be causing some of the 410 Gone errors.
>
> In the meantime, here is a patch to log this case as WEIRD, so that it
> will trigger an incident.

New description:

 The GET Bucket AWS call may return a truncated response, by default after
 1000 objects
 [http://docs.amazonwebservices.com/AmazonS3/latest/API/RESTBucketGET.html
 (doc)]. Currently we don't take that into account (actually I forgot that
 we didn't :-( ), which might be causing some of the 410 Gone errors.

 In the meantime, here is a patch to log this case as WEIRD, so that it
 will trigger an incident.

--

--
Ticket URL: <https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1678#comment:12>
Tahoe-LAFS <https://Tahoe-LAFS.org>
secure decentralized storage