-
Notifications
You must be signed in to change notification settings - Fork 792
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The exporter is many times OOMKilled #834
Comments
What version of the exporter are you using? What flags are you using? What version of elasticsearch? What is the configuration of your elasticsearch cluster (number of nodes and which roles)? |
Thank you for feedback.
v1.6.0
OpenSearch v2.11.0
In larger clusters, where the problem occurring, we have 6 nodes total (2x coordination, 2x manager, 2x data). We using the exporter in small clusters too with only one multirole node, but we not discovered the problem here. |
Indice mappings and shards are both quite a lot of data for any nontrivial cluster (curling the metrics endpoint shows it quite clearly). If you actually want to use these, you will have to significantly raise the memory allocation. In our case, the exporter without these averages ~60MB RAM usage, and ~240MB with them. |
I made some testing and you have right. Memory usage is higher especially on clusters with more indices. Switch It is possible do some optimization on the exporter side? |
Hello.
We discovered, that the exporter is many times OOMKilled. Here you can see many times memory peaks.
I have no clue, why sometimes the exporter need to use more RAM, but by default dont need it.
We have set this resources:
Are there any memory leaks?
The text was updated successfully, but these errors were encountered: