Out of Memory

If you ever face OutOfMemory errors of the Java daemon (which can be found in the amazon-ec2-debug.err file), you are very likely using a high level of concurrency through internal concurrent_threads parameter and/or parallel jobs.

To address this issue, you may consider the following options:

  1. Reduce concurrent_threads parameter.

  2. Reduce the number of jobs running in parallel.

  3. If neither of the above is feasible, you should increase the JVM memory (you may also need to increase the underlying host physical memory)

To increase the JVM memory, you will need to:

Create the following file: /opt/bacula/etc/amazon_rds_backend.conf.

Below, an example of the contents:

Limits file contents
 AMAZON_RDS_JVM_MIN=2G
 AMAZON_RDS_JVM_MAX=8G

Those values will define the MIN (AMAZON_RDS_JVM_MIN) and MAX (AMAZON_RDS_JVM_MAX) memory values assigned to the JVM Heap size. Exercise caution if you are running jobs in parallel, as large values and several jobs at once could quickly consume all available memory on your host.

The /opt/bacula/etc/AMAZON_RDS_backend.conf will remain unchanged during package upgrades, ensuring that your memory configurations are retained.

See also

Next articles:

Go back to: Troubleshooting.