From 5c3509869fbf55d433f600d87abe59cd282e3e01 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Jan=20H=C3=B8ydahl?= Date: Thu, 21 Mar 2024 15:42:35 +0100 Subject: [PATCH] SOLR-16982 Reflect change in reference guide (#2355) (cherry picked from commit ab65dedaf7cffa11c608ba782dd8cc0ea1b2d871) --- .../modules/deployment-guide/pages/circuit-breakers.adoc | 5 +---- 1 file changed, 1 insertion(+), 4 deletions(-) diff --git a/solr/solr-ref-guide/modules/deployment-guide/pages/circuit-breakers.adoc b/solr/solr-ref-guide/modules/deployment-guide/pages/circuit-breakers.adoc index fa2a353c3a9..7ff2ff4d414 100644 --- a/solr/solr-ref-guide/modules/deployment-guide/pages/circuit-breakers.adoc +++ b/solr/solr-ref-guide/modules/deployment-guide/pages/circuit-breakers.adoc @@ -26,10 +26,7 @@ If circuit breakers are enabled, requests may be rejected under the condition of It is up to the client to handle this error and potentially build retry logic as this should be a transient situation. -In a sharded collection, when a circuit breaker trips on one shard, the entire query will fail, -even if the other shard requests succeed. This will multiply the failures seen by the end users. -Setting the `shards.tolerant=true` parameter on requests can help with graceful degradation when -circuit breaker thresholds are reached on some nodes. See the xref:deployment-guide:solrcloud-distributed-requests.adoc#shards-tolerant-parameter[`shards.tolerant` Parameter] for details. +In a request to a sharded collection, the circuit breaker is only checked on the node handling the initial request, not for inter-node requests. It is therefore recommended to load balance client requests across Solr nodes to avoid hotspots. == Circuit Breaker Configurations Circuit breakers can be configured globally for the entire node, or for each collection individually, or a combination. Per-collection circuit breakers are checked before global circuit breakers, and if there is a conflict, the per-collection circuit breaker takes precedence.