Two to three weeks after initial installation, you might notice that eDirectory keeps stopping/restarting itself, depending on monitoring and configuration, under a heavy load – for no apparent reason. You might also get a -150 INSUFFICIENT MEMORY error when you try to back up with dsbk or eMBox. This might be because you did not set a hard cache limit, so edirectory uses a dynamic cache, which causes a memory fillup – and ndsd ends up shutting down.
It’s very important to set a hard limit for the eDirectory Cache on Linux, especially if you’re running Identity Manager engine and drivers. Although I’ve used this solution with Linux, I’m guessing it would apply to all other operating systems, such as UNIX distributions.
How you would set such a limit? One way is to use iMonitor. Or, you can simply create a _ndsdb.ini file in the DIB directory (where nds.01 resides) with content like this:
This sets a hard cache limit of 1 GB and preallocates a limited cache at the beginning of the start process for better performance and lesser fragmentation.
It’s also a good idea to modify /etc/init.d/ndsd to set DHOST_JVM_MAX_HEAP to something greater than 64 MB (default), such as ~ 400 MB (DHOST_JVM_MAX_HEAP=400000000). This is helpful if you’re running the Identity Manager engine and drivers, so that the drivers have more memory to work with.
WARNING: This documents explains how to set values. You should check documentations, run tests and consult related people to find out proper values for your system.
Note that you need to restart ndsd to reflect the changes.