Why is RHDS stuck at 100% CPU when exposed to a bulk load (mainly MOD, MODRDN and DEL on user entries)

Solution Verified - Updated -

Issue

In a single configuration (2 Red Hat Directory Server (RHDS) instances running on 2 servers with replication agreements on each other), when
exposing one instance to a bulk load (mainly MOD, MODRDN and DEL on user entries), after a few times:

  • the RHDS instance seemed not to accept any new request
  • RHDS processes appear stuck at 100% cpu for several minutes

Environment

  • Red Hat Directory Server 9

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content