[
https://issues.apache.org/jira/browse/SOLR-17277?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17848225#comment-17848225
]
Gus Heck edited comment on SOLR-17277 at 5/21/24 2:14 PM:
----------------------------------------------------------
I could imagine use cases:
# The thresholds set are not working out (oops), turn them to warn immediately
(and easily without configuration changes)
# Not having ever felt a need, for actual blocking, but monitor just in case
for peace of mind
# Explore new, stricter limits without causing problems...
The third case is the harder one because you wouldn't want to remove the
existing hard limits. So maybe supporting N thresholds defined as either
warning (with message prefix) or limit and, the ability to turn any threshold
on/warn/off in real time covers all 3. Of course we can also punt any use case
we don't think is important here to simplify...
was (Author: gus_heck):
I could imagine use cases:
# The thresholds set are not working out (oops), turn them to warn immediately
(and easily without configuration changes)
# Not having ever felt a need, for actual blocking, but monitor just in case
for peace of mind
# Explore new, stricter limits without causing problems...
The third case is the harder one because you wouldn't want to remove the
existing hard limits. So maybe supporting N thresholds defined as either
warning (with message prefix) or limit and, the ability to turn any threshold
on/off in real time covers all 3. Of course we can also punt any use case we
don't think is important here to simplify...
> Circuit Breakers should support a "Warn-only" mode
> --------------------------------------------------
>
> Key: SOLR-17277
> URL: https://issues.apache.org/jira/browse/SOLR-17277
> Project: Solr
> Issue Type: Improvement
> Security Level: Public(Default Security Level. Issues are Public)
> Components: Circuit Breakers
> Affects Versions: main (10.0)
> Reporter: Jason Gerlowski
> Priority: Minor
> Labels: newdev
>
> The threshold values used when configuring Circuit Breakers are incredibly
> important. Identifying when load begins to get "dangerous" is tricky: too
> stringent and users will get 429s unnecessarily, too lax and the circuit
> breakers won't be effective at preventing crashes.
> Conservative users may wish to evaluate potential thresholds without actually
> blocking traffic. Could Circuit Breakers offer some sort of "Dry Run"
> capability - where a request that would otherwise have been blocked merely
> logs a message? This would allow users to get feedback on their thresholds
> before they actually start sending CB-based 429s to users.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
