389-ds-base

#47400 MMR stress test with dna enabled causes a deadlock
Closed: wontfix Opened by nhosoi.

Closed: wontfix
Reopen Issue

Steps
1. set up 2way MMR (master/1.3.2 build)
2. enable DNA on both masters
3. Repeat add and delete users from 10 clients
The server hangs in an hour for me.

stacktraces to show the deadlock
deadlock.txt

Bug description: Under the heavy add/delete posix user entries,
dna_update_config_event causes a deadlock.

Fix description: dna_update_config_event starts transaction
before updating the shared config entry to avoid the deadlock
situation.

Reviewed by Rich (Thank you!!)

Pushed to master: commit c6a72a50e6c948647b220e4a44978f2c9c7e8466

Pushed to 389-ds-base-1.3.1: commit 25769aff54247ea80fc9250c53ca4aca1b6493da

Pushed to 389-ds-base-1.3.0: commit d1d2ed05e405a711682e43c465712e0b153a209f

Ticket has been cloned to Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1044141

Metadata Update from @nkinder:
- Issue assigned to nhosoi
- Issue set to the milestone: 1.3.2 - 06/13 (June)

389-ds-base is moving from Pagure to Github. This means that new issues and pull requests
will be accepted only in 389-ds-base's github repository.

This issue has been cloned to Github and is available here:
- https://github.com/389ds/389-ds-base/issues/737

If you want to receive further updates on the issue, please navigate to the github issue
and click on subscribe button.

Thank you for understanding. We apologize for all inconvenience.

Metadata Update from @spichugi:
- Issue close_status updated to: wontfix (was: Fixed)
Metadata
None
None
None
Normal
ack
Community
Static archive. pagure.io was sunset in 2026; this is a read-only snapshot.
Red Hat Logo

Fedora is sponsored by Red Hat. Learn more about the relationship between Red Hat and Fedora »

© Red Hat, Inc. and others.