Difference between revisions of "Data too large, data for"
Jump to navigation
Jump to search
| (5 intermediate revisions by one other user not shown) | |||
| Line 1: | Line 1: | ||
| − | "Caused by: org.elasticsearch.common.breaker.[[CircuitBreakingException]]: [parent] Data too large, data for [indices:monitor/stats[n]] would be [1294815938/1.2gb], which is larger than the limit of [1245184000/1.1gb], real usage: [1294810816/1.2gb], new bytes reserved: [5122/5kb], usages [request=0/0b, fielddata=0/0b, in_flight_requests=5122/5kb, accounting=1135374/1mb]" | + | "Caused by: org.elasticsearch.common.breaker.[[CircuitBreakingException]]: [parent] Data too large, data for [indices:monitor/stats[n]] would be [1294815938/1.2gb], which is larger than the limit of [1245184000/1.1gb], real usage: [1294810816/1.2gb], new bytes reserved: [5122/5kb], usages [request=0/0b, [[fielddata]]=0/0b, in_flight_requests=5122/5kb, accounting=1135374/1mb]" |
| + | "Caused by: org.elasticsearch.common.breaker.CircuitBreakingException: [parent] Data too large, data for [indices:data/read/search[free_context/scroll]] would be [1278122708/1.1gb], which is larger than the limit of [1245184000/1.1gb], real usage: [1278122648/1.1gb], new bytes reserved: [60/60b], usages [request=198852608/189.6mb, fielddata=0/0b, in_flight_requests=60/60b, accounting=1146098/1mb]", | ||
| + | |||
| + | |||
| + | |||
| + | <code>[[Clear SC failed on node]]</code> | ||
== Related == | == Related == | ||
* [[Indice]] | * [[Indice]] | ||
* [[Elasticsearch index]] | * [[Elasticsearch index]] | ||
| + | * [[Elasticseach Index Lifecycle Management (ILM)]] | ||
== See also == | == See also == | ||
Latest revision as of 09:46, 17 January 2023
"Caused by: org.elasticsearch.common.breaker.CircuitBreakingException: [parent] Data too large, data for [indices:monitor/stats[n]] would be [1294815938/1.2gb], which is larger than the limit of [1245184000/1.1gb], real usage: [1294810816/1.2gb], new bytes reserved: [5122/5kb], usages [request=0/0b, fielddata=0/0b, in_flight_requests=5122/5kb, accounting=1135374/1mb]"
"Caused by: org.elasticsearch.common.breaker.CircuitBreakingException: [parent] Data too large, data for [indices:data/read/search[free_context/scroll]] would be [1278122708/1.1gb], which is larger than the limit of [1245184000/1.1gb], real usage: [1278122648/1.1gb], new bytes reserved: [60/60b], usages [request=198852608/189.6mb, fielddata=0/0b, in_flight_requests=60/60b, accounting=1146098/1mb]",
Related[edit]
See also[edit]
- Elasticsearch, installation, ELK, Elastic X-Pack,
elasticsearch.yml, logs, ECK, Elasticsearch curl URLs, Elastisearch REST APIs,/_cat/, /_cluster/, /_xpack/, QueryShardException, Elasticsearch index, ELK backup and restore,elasticsearch-cli, Elasticsearch versions, ElasticSearch Snapshot Lifecycle Management (SLM), Low disk watermark, Elasticsearch storage, Elasticsearch users, Elasticsearch roles, search context, shards, Elastic Cloud, Elastic Licensing, ElasticSearch alerts, ESQL
Advertising:
