-
**Description**
There is a limit of 50 TPS on CreateLogStream operations, after which transactions are throttled [1], described in [2] -
ThrottlingException
The request was denied due to reque…
-
Today, table throttler uses a single metric by which to throttle. This metric is dynamically configurable, but is just the one. The default metric is replication lag, and can be modified based on any …
-
The current throttling mechanism is primitive; it artificially limits throughput even though ZK might be perfectly find to handle and respond to the requests.
E.g. default throttling setting is 50 ca…
-
#### Describe the bug
Default values for GOMAXPROCS cause cgroup CPU throttling.
#### To Reproduce
Steps to reproduce the behavior:
1. Deploy mimir-distributed helm chart using default value…
-
## Description
The authentication routes without rate-limits are open to all kinds of attacks and abuse like:
Brute-Force Attacks:
These attacks involve trying different password combinations r…
-
When I do requests from my local machine, sometimes I get such type of throttle violations:
{
"error_id": 502,
"error_message": "too many requests from this IP, more requests available in 17524 secon…
-
The rate limit system on backend is designed to make it easy to throttle requests. We should make sure this library automatically respects those limits and throttles itself if caller requests more act…
-
The API employs a [rate limit](https://doc.bunq.com/api/1/page/errors), which is understandable.
next to the (outdated?) documentation the following seems to apply:
- endpoint: `device-server/*`…
-
## Steps to reproduce:
1. Trigger a 429 response
## What should happen:
1. You the SDK retries after a few seconds
## What happens:
1. The user has to do this him/her self
## Traceback
[//]: # (I…
-
Hello,
Currently the 429 error pages only has the message "Too Many Requests",
No indication of how much time user has to wait at all! and this is a bad UX IMHO.
For example if user is limited …