[
https://issues.apache.org/jira/browse/SOLR-16974?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17789601#comment-17789601
]
ASF subversion and git services commented on SOLR-16974:
--------------------------------------------------------
Commit f5f54429b34fd71af06b7331cfda070ea56a1580 in solr's branch
refs/heads/branch_9x from Jan Høydahl
[ https://gitbox.apache.org/repos/asf?p=solr.git;h=f5f54429b34 ]
SOLR-16974: Global Circuit Breakers (#1919) (#2070)
Co-authored-by: Christine Poerschke <cpoersc...@apache.org>
(cherry picked from commit e740123546c7f20c6728df42d493e11f93dc8c79)
> Global Circuit Breakers
> -----------------------
>
> Key: SOLR-16974
> URL: https://issues.apache.org/jira/browse/SOLR-16974
> Project: Solr
> Issue Type: New Feature
> Components: Circuit Breakers
> Reporter: Jan Høydahl
> Assignee: Jan Høydahl
> Priority: Major
> Fix For: 9.5
>
> Time Spent: 6.5h
> Remaining Estimate: 0h
>
> Currently Circuit Breakers are configured per core in solrconfig.xml.
> However, cores/collections do not live in isolation, and it could be that a
> cluster administrator would like to enforce circuit breakers for the entire
> cluster.
> I'm not clear as to whether we need both cluster level and a core level
> pluggability. And would core-level breakers add to any cluster-level ones or
> override them for that core?
> A potential design is to add this as a new plugin in solr.xml, and have them
> added in a new static context of CircuitBreakerRegistry. Then the isTripped
> logic would consult both the per-core list and the static/global list of
> breakers.
--
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
