#47410 changelog db deadlocks with DNA and replication
Closed: wontfix None Opened 10 years ago by rmeggins.

steps:
1) configure 3 MMR masters with DNA and range sharing (IPA is probably the easiest way to set this up and consistently cause errors)
2) add a lot of entries to all servers - be sure to exercise the DNA code (again, ipa user-add is probably the easiest way to do this)

You will see errors (very rarely) like this:

_cl5WriteOperationTxn: retry (50) the transaction (csn=XXX) failed (rc=-30994) (Locker was killed to resolve a deadlock)

and the ipa user-add operation will fail


Linked to Bugzilla bug: https://bugzilla.redhat.com/show_bug.cgi?id=975250 (''Red Hat Enterprise Linux 6'')

d1aef99..489de18 389-ds-base-1.2.11 -> 389-ds-base-1.2.11
commit 489de18
Author: Rich Megginson rmeggins@redhat.com
Date: Wed Jun 26 13:35:39 2013 -0600
e1816e8..1987727 389-ds-base-1.3.0 -> 389-ds-base-1.3.0
commit 1987727
Author: Rich Megginson rmeggins@redhat.com
Date: Wed Jun 26 13:35:39 2013 -0600
bf1ec3d..2e1d633 389-ds-base-1.3.1 -> 389-ds-base-1.3.1
commit 2e1d633
Author: Rich Megginson rmeggins@redhat.com
Date: Wed Jun 26 13:35:39 2013 -0600
cce8d34..b573d80 master -> master
commit b573d80
Author: Rich Megginson rmeggins@redhat.com
Date: Wed Jun 26 13:35:39 2013 -0600

Metadata Update from @rmeggins:
- Issue assigned to rmeggins
- Issue set to the milestone: 1.2.11.22

7 years ago

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/747

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)

3 years ago

Login to comment on this ticket.

Metadata