I am currently running Elasticsearch 7.3.2 on a Rasbian (Buster) instance on a Raspberry Pi 4+. It looks like it was running in a green status for a few days, processing files, but suddenly, i noticed a Yellow Status. I looked into gc.log and the file was showing that there is a
Entering Safepoint region: GenCollectForAllocation
Pause Young (Allocation Failure)
Using 4 workers of 4 for Evaluation
Desired survivor size 3342336 bytes, new threshold 6 (max threshold 6)
I am trying to get this back to green, but i am not sure if this is going to be a major issue or not. It does look like it will leave a safepoint region, and then within a fraction of a second will hit it again.
When looking at my mounted NAS, i noticed that it is only 34% full, but im not sure the best approach to solve this
When I ping elasticsearch with: curl localhost:9200/_cat/nodes?pretty
it returns:
{
"error": {
"root_cause": [{
"type": "circuit_breaking_exception",
"reason": "[parent] Data too large, data for [<http request>] would be [1059250992/1010.1mb], which is larger than the limit of [1013704294/966.7mb], real usage: [1059250992/1010.1mb], new bytes reserved: [0/0b], usages [request=0/0b, fielddata=0/0b, in_flight_requests=0/0b, accounting=818200108/780.2mb]",
"bytes_wanted": 1059250992,
"bytes_limit": 1010704294,
"durability": "PERMANENT"
}],
...
"status": 429
}
}
Is this something I can easily resolve in the Elasticsearch yml file in terms of limitations?