#47409 allow setting db deadlock rejection policy
Closed: wontfix Opened by rmeggins.

The deadlock_threadmain DBENV->lock_detect atype is currently hardcoded to DB_LOCK_YOUNGEST which works in most cases. We need the ability to change this.


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

0001-Ticket-47409-allow-setting-db-deadlock-rejection-pol.patch
0001-Ticket-47409-allow-setting-db-deadlock-rejection-pol.patch

Looks good to me.

856cdf8..f754890 389-ds-base-1.2.11 -> 389-ds-base-1.2.11
commit f7548908d4749db429f17e23c01624475c121def
Author: Rich Megginson rmeggins@redhat.com
Date: Tue Jun 25 19:48:17 2013 -0600
693b9f3..42a3ef2 389-ds-base-1.3.0 -> 389-ds-base-1.3.0
commit 42a3ef2644d31355da4d82e1f11b2b2eada554a7
Author: Rich Megginson rmeggins@redhat.com
Date: Tue Jun 25 19:48:17 2013 -0600
91e3ba6..d62cd9b 389-ds-base-1.3.1 -> 389-ds-base-1.3.1
commit d62cd9b69c8a4a852e7bea0345285dc8c3e1e547
Author: Rich Megginson rmeggins@redhat.com
Date: Tue Jun 25 19:48:17 2013 -0600
8bb10ab..4989e77 master -> master
commit 4989e77e2866d53c8bd79a3439b7dd84390cf576
Author: Rich Megginson rmeggins@redhat.com
Date: Tue Jun 25 19:48:17 2013 -0600

forgot flags parameter
f754890..6c1a713 389-ds-base-1.2.11 -> 389-ds-base-1.2.11
commit 6c1a71310292e5992aa1fcc8c203a6b6d595ebe3
Author: Rich Megginson rmeggins@redhat.com
Date: Fri Jun 28 11:37:05 2013 -0600
42a3ef2..e535ff5 389-ds-base-1.3.0 -> 389-ds-base-1.3.0
commit e535ff5a45601c4279a14e92eaf1d68729866d38
Author: Rich Megginson rmeggins@redhat.com
Date: Fri Jun 28 11:37:05 2013 -0600
d62cd9b..ceaa9ac 389-ds-base-1.3.1 -> 389-ds-base-1.3.1
commit ceaa9ac5267c04c23e3fb8e366e17295ffd6b93c
Author: Rich Megginson rmeggins@redhat.com
Date: Fri Jun 28 11:37:05 2013 -0600
4989e77..67cbb2e master -> master
commit 67cbb2eac1300ae57acf75f4c3299103046a3323
Author: Rich Megginson rmeggins@redhat.com
Date: Fri Jun 28 11:37:05 2013 -0600

bc62f82..d1aef99 389-ds-base-1.2.11 -> 389-ds-base-1.2.11
commit d1aef99989c498cde20fc311b05780702efee653
Author: Rich Megginson rmeggins@redhat.com
Date: Tue Jul 2 14:40:00 2013 -0600
e535ff5..1baa10d 389-ds-base-1.3.0 -> 389-ds-base-1.3.0
commit 1baa10dd3c14c6cdc29aae5d114547df812b5c17
Author: Rich Megginson rmeggins@redhat.com
Date: Tue Jul 2 14:40:00 2013 -0600
ceaa9ac..75b9e42 389-ds-base-1.3.1 -> 389-ds-base-1.3.1
commit 75b9e42a6555073d902526c20a606d17fd11f967
Author: Rich Megginson rmeggins@redhat.com
Date: Tue Jul 2 14:40:00 2013 -0600
67cbb2e..989a30b master -> master
commit 989a30bb2d63ee6b9157a9eb6a3d2ff6828abc60
Author: Rich Megginson rmeggins@redhat.com
Date: Tue Jul 2 14:40:00 2013 -0600

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

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

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