Master server becomes unstable or stops

Edit online

The master server might become unstable or stop when it serves a larger number of replica servers. The reason might be because the master server ran out of resources. Follow the steps to resolve this issue.

To resolve this problem, you can set the Ulimits DN entry in the configuration file as shown here:

dn: cn=Ulimits, cn=Configuration
cn: Ulimits
ibm-slapdUlimitDataSegment: -1
ibm-slapdUlimitDescription: Prescribed minimum ulimit option values
ibm-slapdUlimitFileSize: 2097151
ibm-slapdUlimitNofile: 500
ibm-slapdUlimitRSS: -1
ibm-slapdUlimitStackSize: -1
ibm-slapdUlimitVirtualMemory: -1
objectclass: top
objectclass: ibm-slapdConfigUlimit
objectclass: ibm-slapdConfigEntry

Then, configure the system ulimit values to:

core file size     (blocks, -c)    unlimited
data seg size      (kbytes, -d)    unlimited
file size          (blocks, -f)    unlimited
max memory size    (kbytes, -m)    unlimited
open files         (-n)            30000
pipe size          (512 bytes, -p) 64
stack size         (kbytes, -s)    unlimited
cpu time           (seconds, -t)   unlimited
max user processes (-u)            262144
virtual memory     (kbytes, -v)    unlimited

Restart the servers for the changes to take effect.