[
https://issues.apache.org/jira/browse/SOLR-16974?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17765571#comment-17765571
]
Eric Pugh commented on SOLR-16974:
----------------------------------
Nothing per se. And honestly, this is one of the areas that has me a bit
stumped. I've mostly been able to move logic over to Java when it didn't
really touch anything on the OS level, like the ENV variables. I made great
progress though some like assert, api, create_collection, and then it got hard
as I started looking at "stop" and "start" and friends because of the OS level
logic. Which I didn't feel comfortable changing around...
If you make progress, this might actually unblock me a bit...
> Global Circuit Breakers
> -----------------------
>
> Key: SOLR-16974
> URL: https://issues.apache.org/jira/browse/SOLR-16974
> 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
> Time Spent: 0.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: [email protected]
For additional commands, e-mail: [email protected]
