Hello Markrafa,
It seems that the error has its origin in the prevention of an OutOfMemory problem. This usually occurs when the heap of the Elasticsearch JVM is at maximum usage and more memory than is available is requested to perform certain operations.
If this is the problem it is related to Elasticsearch resources. The heap configuration is limited. We would have to see if you can increase the heap memory depending on the resources of your Elasticsearch host.
Could you provide us with the resources available to the Elasticsearch host and /etc/elasticsearch/jvm.options content.?
We would be interested in the following section:
################################################################
## IMPORTANT: JVM heap size
################################################################
. . .
# Xms represents the initial size of total heap space
# Xmx represents the maximum size of total heap space
In this section, you will have the values assigned to the heap of the Elasticsearch JVM. Normally it is given a maximum and minimum value equal to half of the RAM available to Elasticsearch. For example, if your Elasticsearch host has 8GB RAM you should have heap memory like this:
-Xms4g
-Xmx4g
If you have other values less than half of your RAM, try increasing it and restarting the Elasticsearch service for the changes to take effect.
I hope this is helpful. If this is not the problem, let us know and we will look into the problem further.
Regards,
Alfonso Ruiz-Bravo