From 360b09f14858d8062d79053115c6366eafd6af8e Mon Sep 17 00:00:00 2001 From: Colin Goodheart-Smithe Date: Mon, 4 Jun 2018 09:19:38 +0100 Subject: [PATCH] [DOCS] Fixes accounting setting names (#30863) The documentation for the account circuit breaker listed the settings for it's limit and overhead to be `network.breaker.accounting.limit` and `network.breaker.accounting.overhead` when in `HieratchyCircuitBreakerService` it seems the settings are actually `indices.breaker.accounting.limit` and `indices.breaker.accounting.overhead`. --- docs/reference/modules/indices/circuit_breaker.asciidoc | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/reference/modules/indices/circuit_breaker.asciidoc b/docs/reference/modules/indices/circuit_breaker.asciidoc index 3df187086bb..03cdb307b9f 100644 --- a/docs/reference/modules/indices/circuit_breaker.asciidoc +++ b/docs/reference/modules/indices/circuit_breaker.asciidoc @@ -80,12 +80,12 @@ The accounting circuit breaker allows Elasticsearch to limit the memory usage of things held in memory that are not released when a request is completed. This includes things like the Lucene segment memory. -`network.breaker.accounting.limit`:: +`indices.breaker.accounting.limit`:: Limit for accounting breaker, defaults to 100% of JVM heap. This means that it is bound by the limit configured for the parent circuit breaker. -`network.breaker.accounting.overhead`:: +`indices.breaker.accounting.overhead`:: A constant that all accounting estimations are multiplied with to determine a final estimation. Defaults to 1