OOM Killer Issues Troubleshooting

Common recommendationsTake a look at the primary settings for managing memory in your Java setup. If necessary, tweak them to suit your specific application requirements. For instance:

When you set up your Java environment, consider adjusting memory allocation using parameters like:

java -Xmx2048m -Xms256m

Here’s what these flags mean:

The Xmx flag determines the maximum heap memory the Java Virtual Machine (JVM) can use.

The Xms flag sets the initial memory allocation pool.

Related processes

Common recommendations1. If you’re facing an issue with the httpd (httpd.itk) service, here’s what you can do to fix it:

• Start by checking how much RAM each httpd instance is using on average.
• Look into the /etc/httpd/httpd.conf file and remove any Jelastic autoconfiguration marks you find.
• Adjust the ServerLimit and MaxClients values using this formula: (Total RAM – 5%) / Average RAM.

2. To check the size of php-fpm instances within your nginx process, hop into your container through SSH and give a look using tools like ps or top. Here’s a simple guide:

• If you notice that each php-fpm instance is gobbling up around 50-100Mb of RAM, it’s time to take action. Consider turning off auto-configuration and reducing the max_children parameter.
• However, if you find that the sizes of instances are all over the place or surpassing 200-300Mb, there might be a leak somewhere in your process. It’s advisable to dig into your code, spot the issue, and optimize it. Alternatively, you can also opt to disable auto-configuration and trim down the max_requests_per_child parameter.

Related processes

Common recommendationsMemory leaks are something Ruby developers often encounter. Start by going over and optimising your code before taking on this. Another approach could be raising the RAM limit for your instance.

Related processes

Common recommendations1. If you’re encountering issues with the httpd (httpd.itk) service, you can troubleshoot by adjusting the server’s memory management settings in the following manner:

• First, check the average RAM consumption of each httpd instance.
• Next, locate and remove the Jelastic autoconfiguration mark found in the /etc/httpd/httpd.conf file.
• Then, tweak the ServerLimit and MaxClients values. You may compute these values using the following formula: (Total RAM – 5%) / Average RAM.

2. If not, you might want to consider giving the node more RAM. Sometimes, the main Python process simply needs extra memory to run smoothly.

Related processes

Common recommendationsIf you’re having trouble with a process getting killed, try restarting the container. If the problem persists, adding more RAM to the node may assist. Sometimes, certain applications need more memory to run smoothly.

Related processes

1. If you’re working with the InnoDB engine, which has been included since MySQL version 5.5, you’ll want to keep an eye on buffer sizes. This can be done by running the following command:SHOW ENGINE INNODB STATUS\G;

If you notice that the buffers are taking up a significant portion of your server’s RAM (over 80%), it’s a good idea to adjust the size of the buffer pool. You can do this by tweaking the innodb_buffer_pool_size parameter in the /etc/my.cnf file. Alternatively, if the buffers aren’t using up too much RAM, consider allocating more memory to your server.

2. Additionally, it’s wise to regularly check the MySQL logs for any warnings or recommendations.

Related processes

Common recommendationsIf you’re encountering an issue with the httpd service, you can try tweaking some server memory settings:

First off, take a look at how much RAM each httpd instance is gobbling up on average.

Next, go into the /etc/httpd/httpd.conf file and hunt down the Jelastic autoconfiguration mark. Get rid of it.

Lastly, decrease the ServerLimit and MaxClients values. A good rule of thumb is to use this formula: (Total_RAM – 5%) / Average_RAM to figure out the new values.

Note: If you see that the memory use keeps going up for each thing running (we call this a “leak”), try reducing the MaxRequestsPerChild setting to somewhere between 1000 and 5000.

Related processes

Common recommendationsIncrease the amount of RAM assigned to the relevant node since the services it manages may simply need additional memory to function properly.

Related processes

Common recommendationsIncrease the amount of RAM assigned to the relevant node since the services it manages may simply need additional memory to function properly.

Related processes