Hi!
We have a Headless Drupal 9 site (FE: Gatsby) with Elasticsearch that's currently encountering [circuit_breaking_exception] when doing a search. As per some discussions it is suggested we adjust the Heap size on Production but not sure on where should we adjust it. We were able to adjust it on the docker-compose.elasticsearch.yml by defining "ES_JAVA_OPTS=-Xms1g -Xmx1g" on file, but this is only for ddev/local instances. Can you provide us some inputs on how we can adjust this on the Production site or some recommended performance adjustments?
Error on site:
{
"error": {
"root_cause": [
{
"type": "circuit_breaking_exception",
"reason": "[parent] Data too large, data for [<http_request>] would be [412221276/393.1mb], which is larger than the limit of [408420352/389.5mb], real usage: [412218440/393.1mb], new bytes reserved: [2836/2.7kb], usages [request=192/192b, fielddata=4449/4.3kb, in_flight_requests=2836/2.7kb, model_inference=0/0b, accounting=273048/266.6kb]",
"bytes_wanted": 412221276,
"bytes_limit": 408420352,
"durability": "PERMANENT"
}
],
"type": "circuit_breaking_exception",
"reason": "[parent] Data too large, data for [<http_request>] would be [412221276/393.1mb], which is larger than the limit of [408420352/389.5mb], real usage: [412218440/393.1mb], new bytes reserved: [2836/2.7kb], usages [request=192/192b, fielddata=4449/4.3kb, in_flight_requests=2836/2.7kb, model_inference=0/0b, accounting=273048/266.6kb]",
"bytes_wanted": 412221276,
"bytes_limit": 408420352,
"durability": "PERMANENT"
},
"status": 429
}
Here's the current data on the Stack Monitoring page:
Really appreciate any input here, Thank you!