diff options
| author | staebler <staebler@redhat.com> | 2017-08-21 17:19:44 -0400 |
|---|---|---|
| committer | staebler <staebler@redhat.com> | 2017-08-21 17:19:44 -0400 |
| commit | fd4e14f00e339be77d5433edbe18d79a3f834cc5 (patch) | |
| tree | 428514f688464f1f6baefbadecc73bfa877e6b2e | |
| parent | e0ed46a691296d5ad8d531eb329e973ab63b8a33 (diff) | |
Include information about client behavior when faced with a 429 response due to event rate limiting.
| -rw-r--r-- | contributors/design-proposals/admission_control_event_rate_limit.md | 8 |
1 files changed, 8 insertions, 0 deletions
diff --git a/contributors/design-proposals/admission_control_event_rate_limit.md b/contributors/design-proposals/admission_control_event_rate_limit.md index f7180e00..48f1ab9b 100644 --- a/contributors/design-proposals/admission_control_event_rate_limit.md +++ b/contributors/design-proposals/admission_control_event_rate_limit.md @@ -139,3 +139,11 @@ The allowance and eviction for per-user and per-source+object rate limiting works identically to the per-namespace rate limiting, with the exception that the former consider the user or source+object of the event and the latter considers the namespace of the event request. + +## Client Behavior + +Currently, the Client event recorder treats a 429 response as http transport +type of error, that warrants retrying the event request. Instead, the event +recorder should abandon the event. Additionally, the event recorder should +abandon all future events for the period of time specified in the +retryAfterSeconds field of the 429 response. |