OpenStack Object Storage (swift)

  1. Bug #1669888
  2. Comment #6

Comment 6 for bug 1669888

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Related fix merged to swift (master)

Reviewed: https://review.opendev.org/697535
Committed: https://git.openstack.org/cgit/openstack/swift/commit/?id=f33c061ae92f33ea467c58749d3f15d2b1cc942c
Submitter: Zuul
Branch: master

commit f33c061ae92f33ea467c58749d3f15d2b1cc942c
Author: Tim Burke <email address hidden>
Date: Thu Dec 5 09:42:33 2019 -0800

    s3api: Better handle 498/429 responses

    Currently, they just 500 as an unexpected response status. Much better
    would be S3's '503 Slow Down' response.

    Of course, that's all dependent on where you place ratelimit in your
    pipeline -- and we haven't really given clear guidance on that. I'm not
    actually sure you *want* ratelimit to be after s3api and auth... but if
    you *do*, let's at least handle it gracefully.

    Change-Id: I36f0954fd9949d7d1404a0c381b917d1cfb17ec5
    Related-Bug: 1669888