[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:  new
     Priority:  critical      |  Milestone:  soon
    Component:  code-storage  |    Version:  1.9.0-s3branch
   Resolution:                |   Keywords:  s3-backend 410 reviewed
Launchpad Bug:                |
------------------------------+-------------------------------------

Comment (by davidsarah):

 I implemented prefix queries (so we no longer list ''all'' objects in the
 bucket and filter, which needed to be fixed anyway). That seems to be
 working, and has given a measurable performance improvement of ~0.44
 seconds per DHYB on secorp's server, but, it didn't stop the truncated
 responses as I expected. We no longer get lots of truncated responses with
 at or near 1000 objects, but we do still get occasional truncated
 responses with 0 or 1 objects. This makes no sense and is contrary to the
 S3 API documentation. Frustrating.

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