OpenStack Compute (Nova)

No retry-after guidance provided to throttled clients

Reported by Eoghan Glynn on 2012-02-28
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Compute (nova)
High
Eoghan Glynn

Bug Description

When rate limits are exceeded, a 413 response is emitted in order to throttle back the client.

This should include a retry-after hint to guide the caller's redrive strategy.

The absence of this header means the client would be forced to parse the overLimitFault details string in order to make a sensible decision as to when it would make sense to redrive the request.

Eoghan Glynn (eglynn) on 2012-02-28
Changed in nova:
assignee: nobody → Eoghan Glynn (eglynn)
status: New → In Progress

Reviewed: https://review.openstack.org/4645
Committed: http://github.com/openstack/nova/commit/8bc87c62a118c75a6cbf69c0edfa3ba5acbf3950
Submitter: Jenkins
Branch: master

commit 8bc87c62a118c75a6cbf69c0edfa3ba5acbf3950
Author: Eoghan Glynn <email address hidden>
Date: Tue Feb 28 20:22:19 2012 +0000

    Provide retry-after guidance on throttled requests

    Fixes bug 942874

    Guide the caller's redrive strategy with a Retry-After hint in
    the 413 response emitted when rate limits are exceeded.

    The simplest format of Retry-After is used, i.e. number of seconds
    as opposed to a HTTP time string.

    Change-Id: I8b1a28f964a111008b1a88d9c0f96c5a0abd8314

Changed in nova:
status: In Progress → Fix Committed
Brian Waldon (bcwaldon) on 2012-02-29
Changed in nova:
importance: Undecided → High
milestone: none → essex-4

Reviewed: https://review.openstack.org/4706
Committed: http://github.com/openstack/nova/commit/10c58c6e81ed8623091231fb1ef65c8529b43fe1
Submitter: Jenkins
Branch: milestone-proposed

commit 10c58c6e81ed8623091231fb1ef65c8529b43fe1
Author: Eoghan Glynn <email address hidden>
Date: Tue Feb 28 20:22:19 2012 +0000

    Provide retry-after guidance on throttled requests

    Fixes bug 942874

    Guide the caller's redrive strategy with a Retry-After hint in
    the 413 response emitted when rate limits are exceeded.

    The simplest format of Retry-After is used, i.e. number of seconds
    as opposed to a HTTP time string.

    Change-Id: I8b1a28f964a111008b1a88d9c0f96c5a0abd8314

Changed in nova:
status: Fix Committed → Fix Released
Thierry Carrez (ttx) on 2012-04-05
Changed in nova:
milestone: essex-4 → 2012.1
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers