Memory Leak Processes

Memory Leak Processes

OOM Killer Resolutions: Processes with High Risk of Memory Leak

Pay special attention to the processes in this group as to the most probable cause of your out-of-memory issues (sorted based on server role):

Allocate more RAM to a corresponding node – handled services could just require more memory for normal operability.

Process Resolution
varnishd Allocate more RAM to a node – handled services could just require more memory for normal operability

Click on points within the list below to view some common recommendations on dealing with memory shortage issues considering used programming language, as well as appropriate resolutions for the most demanding related processes:

  • Java
  • PHP
  • Ruby
  • Python
  •  
    NodeJS

     

Click on the required DB stack within the list below to reveal appropriate common recommendations on coping with OOM issues, as well as resolutions for particular killed processes:

  • MySQL
  • MongoDB
  • PostgreSQL
  •  
    Redis

     

Processes in this section can be run and, subsequently, killed within different node types. Thus, OOM resolutions for them vary and depend on a process itself – see the table below to find the appropriate recommendations.

Process Stack Resolution
httpd PHP
Ruby
Python
MySQL
MongoDB
PostgreSQL
1. Check the average amount of RAM, used by each httpd instance
2. Remove the Jelastic autoconfiguration mark within the /etc/httpd/httpd.conf file
3. Decrease ServerLimit and MaxClients values according to the formula: (Total_RAM – 5%) / Average_RAM
lsyncd PHP
NodeJS
Python
Allocate more RAM to a node – handled services could just require more memory for normal operability
httpd.itk PHP
Ruby
Python
1. Check the average amount of RAM, used by each httpd instance
2. Remove the Jelastic autoconfiguration mark within the /etc/httpd/httpd.conf file
3. Decrease ServerLimit and MaxClients values according to the formula: (Total_RAM – 5%) / Average_RAM
procmail Any Restart container in order to restore the process
vsftpd Any Restart container in order to restore the process
yum Any Restart container in order to restore the process
cc1 3rd party Allocate more RAM to a node – handled services could just require more memory for normal operability
clamd 3rd party Allocate more RAM to a node – handled services could just require more memory for normal operability
ffmpeg 3rd party Allocate more RAM to a node – handled services could just require more memory for normal operability
firefox 3rd party Allocate more RAM to a node – handled services could just require more memory for normal operability
newrelic-daemon 3rd party Restart the main stack service (nginx, tomcat, nodejs, etc)