search

kinu-garage / hut_10sqft

Computer setup tools for my own environment, and public discussion place holder.
2 stars 1 forks source link

Nagios Log Server using too much RAM #463

Open 130s opened 4 years ago

130s commented 4 years ago

As part of #455

https://support.nagios.com/forum/viewtopic.php?f=38&t=40512

Is it normal that the RAM is fully used?

i have searched in the forum and have set the ES_HEAP_SIZE to 4g But the RAM is still full. The Image is attached. My ressources 10g RAM Intel Xeon 4 Cores eSXI VM-Ware

Yes, this is to be expected. Java is a hog, and from my understanding pre-allocates memory to use at it's own will. With that, NLS's main consumption is going to be ram as it will cache your logs here, to allow quick viewing through them all.

:

You can hard-code memory/heap limits in Java for elasticsearch and logstash, but we do not recommend this.

If you are unsatisfied with the amount of memory your machine is using, your primary options are to either increase the available physical memory (Java does not use SWAP very effectively) or reduce the number of open indices. The open indices are what consume the most RAM since open indices are stored in RAM for quick searching/processing. Elasticsearch is, by design, a memory hog.

This thread is 4 years old so using my trial account on the forum I asked a question (it needs approved so I don' have a link to it for now...What a dinasaur system).

130s commented 4 years ago

For now on the laptop the Server starts on, I manually kill all the processes (sudo systemctl status nagios doesn't seem to stop the Log Server processes).