Search

3.2. Avoiding Data Corruption by Monitoring Free Database Locks

download PDF
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:
  1. For example, to set the interval to 600 milliseconds and the threshold to 85 percent, enter:
    # dsconf -D "cn=Directory Manager" ldap://server.example.com backend config set --locks-monitoring-enabled on --locks-monitoring-pause 600 --locks-monitoring-threshold 85
    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 next monitoring check happens. Setting a too short interval can slow down the server.
  2. Restart the instance:
    # dsctl instance_name restart
Red Hat logoGithubRedditYoutubeTwitter

Learn

Try, buy, & sell

Communities

About Red Hat Documentation

We help Red Hat users innovate and achieve their goals with our products and services with content they can trust.

Making open source more inclusive

Red Hat is committed to replacing problematic language in our code, documentation, and web properties. For more details, see the Red Hat Blog.

About Red Hat

We deliver hardened solutions that make it easier for enterprises to work across platforms and environments, from the core datacenter to the network edge.

© 2024 Red Hat, Inc.