M
Elasticsearch CircuitBreakingException 错误解决方案
# Elasticsearch CircuitBreakingException 错误解决方案100.00% 偶尔会报错,报错信息为:100.00% ```java org100.00% .elasticsearch.common100.00% .breaker100.00% .CircuitBreakingException: [parent] Data too large, data for [] would be [260230692/248100.00% .1mb], which is larger than the limit of [255013683/243.1mb], real usage: [260230552/248.1mb], new bytes reserved: [140/140b], usages [request=0/0b, fielddata=650/650b, in_flight_requests=140/140b, accounting=132300/129.1kb]100.00% at org.elasticsearch.indices.breaker.HierarchyCircuitBreakerService.checkParentLimit(HierarchyCircuitBreakerService.java:343)100.00% ``` **原因**:100.00% field data 的缓存不够用100.00% **临时解决方案**100.00% Kibana Dev Tools100.00% ```java PUT _cluster/settings { "persistent" : {100.00% "indices.breaker.fielddata.limit" : "40%" 100.00% } } ``` **终极解决方案**100.00% 加内存 原先给的256m 咋调参数都会报错,狠心又扩了8G的内存,给重新分了4G的内存,终于不报错了o(╥﹏╥)o96.67%