Red Hat SummitEste conteúdo não está disponível no idioma selecionado.
Chapter 4. Tuning the number of BDB locks
When a Directory Server instance uses Berkeley Database (BDB), lock mechanism controls how many copies of Directory Server processes can run at the same time. For example, during an import job, Directory Server sets a lock in the /run/lock/dirsrv/slapd-instance_name/imports/ directory to prevent the ns-slapd Directory Server process, another import, or export operations from running.
If the server runs out of available locks, Directory Server logs the following error in the /var/log/dirsrv/slapd-instance_name/errors file:
libdb: Lock table is out of available locks
libdb: Lock table is out of available locksHowever, the Directory Server default settings try to prevent the server from running out of locks to avoid data corruption. For details, see Avoiding data corruption by monitoring free database locks
4.1. Avoiding data corruption by monitoring free BDB database locks
Running out of Berkeley Database (BDB) locks can lead to data corruption. To avoid this, Directory Server, by default, monitors the remaining number of free locks every 500 milliseconds and, if the number of active database locks is equal or higher than the 90%, Directory Server stops all searches.
The following procedure changes the interval to 600 milliseconds and the threshold to 85 percent.
If you set a too high interval, the server can run out of locks before the next monitoring check happens. Setting a too short interval can slow down the server.
Prerequisites
- The Directory Server instance uses BDB.
Procedure
Set the interval and threshold:
dsconf instance_name backend config set --locks-monitoring-enabled on --locks-monitoring-pause 600 --locks-monitoring-threshold 85
# dsconf instance_name backend config set --locks-monitoring-enabled on --locks-monitoring-pause 600 --locks-monitoring-threshold 85Copy to Clipboard Copied! Toggle word wrap Toggle overflow Restart the instance:
dsctl instance_name restart
# dsctl instance_name restartCopy to Clipboard Copied! Toggle word wrap Toggle overflow
Verification
Display the locks monitoring settings:
dsconf -D "cn=Directory Manager" ldap://supplier.example.com backend config get | grep "nsslapd-db-locks-monitoring"
# dsconf -D "cn=Directory Manager" ldap://supplier.example.com backend config get | grep "nsslapd-db-locks-monitoring" nsslapd-db-locks-monitoring-enabled: on nsslapd-db-locks-monitoring-threshold: 85 nsslapd-db-locks-monitoring-pause: 600Copy to Clipboard Copied! Toggle word wrap Toggle overflow
4.2. Manually monitoring the number of BDB locks
Directory Server tracks the current number of Berkeley Database (BDB) locks in the nsslapd-db-current-locks and nsslapd-db-max-locks attributes in cn=database,cn=monitor,cn=ldbm database,cn=plugins,cn=config.
Prerequisites
- The Directory Server instance uses BDB.
Procedure
To display the number of locks, enter:
ldapsearch -D "cn=Directory Manager" -W -H ldap://server.example.com -x -s sub -b "cn=database,cn=monitor,cn=ldbm database,cn=plugins,cn=config" nsslapd-db-current-locks nsslapd-db-max-locks
# ldapsearch -D "cn=Directory Manager" -W -H ldap://server.example.com -x -s sub -b "cn=database,cn=monitor,cn=ldbm database,cn=plugins,cn=config" nsslapd-db-current-locks nsslapd-db-max-locks ... nsslapd-db-current-locks: 37 nsslapd-db-max-locks: 39Copy to Clipboard Copied! Toggle word wrap Toggle overflow
4.3. Setting the number of BDB locks using the command line
Use the dsconf backend config set command to update the number of Berkeley Database (BDB) locks that Directory Server can use.
Prerequisites
- The Directory Server instance uses BDB.
Procedure
Set the number of locks:
dsconf instance_name backend config set --locks=20000
# dsconf instance_name backend config set --locks=20000Copy to Clipboard Copied! Toggle word wrap Toggle overflow The command sets the number of locks to
20000.Restart the instance:
dsctl instance_name restart
# dsctl instance_name restartCopy to Clipboard Copied! Toggle word wrap Toggle overflow
Verification
Display the value of the
nsslapd-db-locksparameter:dsconf instance_name backend config get | grep "nsslapd-db-locks:"
# dsconf instance_name backend config get | grep "nsslapd-db-locks:" nsslapd-db-locks: 20000Copy to Clipboard Copied! Toggle word wrap Toggle overflow
4.4. Setting the number of BDB locks using the web console
You can set the number of Berkeley Database (BDB) locks that Directory Server uses in the global database configuration in the web console.
Prerequisites
- You are logged in to the instance in the web console.
- The Directory Server instance uses BDB.
The following procedure sets the number of locks to 2000.
Procedure
-
Navigate to
. -
Update the Database Locks field to
2000. - Click .
-
Click
.
Verification
-
Verify that the new value is present in
.
'%20d='M201.5%20305.5c-13.8%200-24.9-11.1-24.9-24.6%200-13.8%2011.1-24.9%2024.9-24.9%2013.6%200%2024.6%2011.1%2024.6%2024.9%200%2013.6-11.1%2024.6-24.6%2024.6zM504%20256c0%20137-111%20248-248%20248S8%20393%208%20256%20119%208%20256%208s248%20111%20248%20248zm-132.3-41.2c-9.4%200-17.7%203.9-23.8%2010-22.4-15.5-52.6-25.5-86.1-26.6l17.4-78.3%2055.4%2012.5c0%2013.6%2011.1%2024.6%2024.6%2024.6%2013.8%200%2024.9-11.3%2024.9-24.9s-11.1-24.9-24.9-24.9c-9.7%200-18%205.8-22.1%2013.8l-61.2-13.6c-3-.8-6.1%201.4-6.9%204.4l-19.1%2086.4c-33.2%201.4-63.1%2011.3-85.5%2026.8-6.1-6.4-14.7-10.2-24.1-10.2-34.9%200-46.3%2046.9-14.4%2062.8-1.1%205-1.7%2010.2-1.7%2015.5%200%2052.6%2059.2%2095.2%20132%2095.2%2073.1%200%20132.3-42.6%20132.3-95.2%200-5.3-.6-10.8-1.9-15.8%2031.3-16%2019.8-62.5-14.9-62.5zM302.8%20331c-18.2%2018.2-76.1%2017.9-93.6%200-2.2-2.2-6.1-2.2-8.3%200-2.5%202.5-2.5%206.4%200%208.6%2022.8%2022.8%2087.3%2022.8%20110.2%200%202.5-2.2%202.5-6.1%200-8.6-2.2-2.2-6.1-2.2-8.3%200zm7.7-75c-13.6%200-24.6%2011.1-24.6%2024.9%200%2013.6%2011.1%2024.6%2024.6%2024.6%2013.8%200%2024.9-11.1%2024.9-24.6%200-13.8-11-24.9-24.9-24.9z'/%3e%3c/svg%3e){kind=small}