3.2. Avoiding Data Corruption by Monitoring Free Database Locks
3.2. Avoiding Data Corruption by Monitoring Free Database Locks Running out of database locks can lead to data corruption. To avoid this, Directory Server, by default, monitors the remaining number of free database locks every 500 milliseconds and, if the number of active database locks is equal or higher than the 90%, Directory Server aborts all searches. You can change the interval and threshold: For example, to set the interval to 600 milliseconds and the threshold to 85 percent, enter: The --locks-monitoring-enabled on option ensure that the feature is enabled. Note If you set a too high interval, the server can run out of locks before the monitoring check happens. Setting a too short interval can slow down the server. Restart the instance:
dsconf -D "cn=Directory Manager" ldap://server.example.com backend config set --locks-monitoring-enabled on --locks-monitoring-pause 600 --locks-monitoring-threshold 85 dsctl instance_name restart