[
https://issues.apache.org/jira/browse/SOLR-16954?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17762779#comment-17762779
]
Jan Høydahl commented on SOLR-16954:
------------------------------------
Yea, an example is
[https://ci-builds.apache.org/job/Solr/job/Solr-Check-main/7905/testReport/org.apache.solr.util/TestCircuitBreaker/classMethod/]
Looks like we enabled a 75% Memory Circuit Breaker for update requests that is
not really needed/exercised by any tests. And the Jenkins machine is probably
more likely to trip this than randome local tests? I'm going to remove the
update breaker in solrconfig-pluggable-circuitbreaker.xml since these are
tested programmatically with "Mock/Fake" subclasses.
> Circuit breaker for update requests
> -----------------------------------
>
> Key: SOLR-16954
> URL: https://issues.apache.org/jira/browse/SOLR-16954
> Project: Solr
> Issue Type: New Feature
> Security Level: Public(Default Security Level. Issues are Public)
> Components: Circuit Breakers
> Reporter: Jan Høydahl
> Assignee: Jan Høydahl
> Priority: Major
> Fix For: 9.4
>
> Time Spent: 50m
> Remaining Estimate: 0h
>
> Provide a way to utilize any circuit breaker for update requests.
> The idea is that any CircuitBreaker plugin should be able to register for
> SEARCH and/or UPDATE request types. The CB registry will keep track of these
> individually and provide methods to poll whether a CB has tripped for the
> given request type.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org
For additional commands, e-mail: issues-h...@solr.apache.org
