Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Throttling failure response status shall be configurable

See original GitHub issue

Currently 503 - Service Unavailable failure response status hardcoded by com.linecorp.armeria.server.throttling.ThrottlingService. The response status should be driven by the configured strategy and it shall permit using 429 - Too Many Requests as a more appropriate and more common throttling status.

Issue Analytics

State:
Created 4 years ago
Comments:9 (4 by maintainers)

Top GitHub Comments

4reactions

trustincommented, Feb 13, 2020

Agreed, @max904-github. Any objections? /cc @minwoox @ikhoon @imasahiro @kojilin @anuraaga ?

0reactions

max904-githubcommented, Feb 17, 2020

Posted a PR. Kept the default to SERVICE_UNAVAILABLE.

Top Results From Across the Web

Errors related to the sending quotas for your Amazon SES ...

If you encounter a throttling error, you should program your application to wait for an interval of up to 10 minutes, and then...

Request limits and throttling - Azure Resource Manager

Describes how to use throttling with Azure Resource Manager requests when subscription limits have been reached.

HTTP Status Codes: All 63 explained - including FAQ & Video

HTTP status codes are three-digit responses from the server to the browser-side request. Everyone has probably gotten the classic 404 page-not-found error.

Retries — Boto3 Docs 1.26.26 documentation - Amazon AWS

Retry attempts on several HTTP status codes, including 429, 500, 502, 503, 504, and 509. Any retry attempt will include an exponential backoff...

Rate limit — envoy 1.25.0-dev-5db678 documentation

If there is an error in calling rate limit service or rate limit service returns an error and failure_mode_deny is set to true,...