-
Notifications
You must be signed in to change notification settings - Fork 26
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support retries on rate limited batches #192
Labels
enhancement
New feature or request
Comments
Hi @acm19, thanks for reporting this! I guess the support for retry on 429 should go in conjunction with adding a config param similar to Yes, contributions are welcome. Just leave a note in this issue that you are going to implement a solution by yourself. |
acm19
pushed a commit
to acm19/loki-logback-appender
that referenced
this issue
Nov 23, 2023
Adds an option to enable/disable retries on rate limit errors: `dropRateLimitedBatches`. It's enabled by default to keep consistency with Promtail options. Also because Loki scales less aggressively and relies on retries when the load is spiky. Resolves: loki4j#192
acm19
added a commit
to acm19/loki-logback-appender
that referenced
this issue
Nov 23, 2023
Adds an option to enable/disable retries on rate limit errors: `dropRateLimitedBatches`. It's enabled by default to keep consistency with Promtail options. Also because Loki scales less aggressively and relies on retries when the load is spiky. Resolves: loki4j#192
Hey @nehaev , I've created a PR, let me know your thoughts. |
acm19
added a commit
to acm19/loki-logback-appender
that referenced
this issue
Nov 24, 2023
Adds an option to enable/disable retries on rate limit errors: `dropRateLimitedBatches`. It's enabled by default to keep consistency with Promtail options. Also because Loki scales less aggressively and relies on retries when the load is spiky. Resolves: loki4j#192
acm19
added a commit
to acm19/loki-logback-appender
that referenced
this issue
Nov 24, 2023
Adds an option to enable/disable retries on rate limit errors: `dropRateLimitedBatches`. It's enabled by default to keep consistency with Promtail options. Also because Loki scales less aggressively and relies on retries when the load is spiky. Resolves: loki4j#192
acm19
added a commit
to acm19/loki-logback-appender
that referenced
this issue
Nov 27, 2023
Adds an option to enable/disable retries on rate limit errors: `dropRateLimitedBatches`. It's enabled by default to keep consistency with Promtail options. Also because Loki scales less aggressively and relies on retries when the load is spiky. Resolves: loki4j#192
acm19
added a commit
to acm19/loki-logback-appender
that referenced
this issue
Nov 28, 2023
Adds an option to enable/disable retries on rate limit errors: `dropRateLimitedBatches`. It's enabled by default to keep consistency with Promtail options. Also because Loki scales less aggressively and relies on retries when the load is spiky. Resolves: loki4j#192
nehaev
pushed a commit
that referenced
this issue
Nov 30, 2023
Adds an option to enable/disable retries on rate limit errors: `dropRateLimitedBatches`. It's enabled by default to keep consistency with Promtail options. Also because Loki scales less aggressively and relies on retries when the load is spiky. Resolves: #192
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Allow to retry on HTTP 429, currently retries
AsyncBufferPipeline#checkIfEligibleForRetry
are performed on connection errors or HTTP 503. It'd be great to be able to retry when we get rate limited. This would be similar todrop_rate_limited_batches
in Promtail.Also, are you open to contributions?
The text was updated successfully, but these errors were encountered: