The scenario of deadlock requires at least 3 thread
MOD(cn=schema) hold StateChange lock wait for vattr lock # It can be a MOD done by schema learning SRCH hold vattr lock wait for DB page MOD hold DB page wait for StateChange lock
it can occurs on 1.2, 1.3 It could occur on 1.4.* but the dynamic is changed by others vattr changes, should be very rare
tbd
it deadlocks indefinitely
Should not deadlock
Metadata Update from @tbordaz: - Custom field origin adjusted to IPA - Custom field reviewstatus adjusted to None - Custom field rhbz adjusted to https://bugzilla.redhat.com/show_bug.cgi?id=1824930
PR https://pagure.io/389-ds-base/pull-request/51069
151a967 .. 1b7b12e master
Metadata Update from @tbordaz: - Issue assigned to tbordaz
Metadata Update from @mreynolds: - Issue priority set to: major - Issue set to the milestone: 1.4.1
Metadata Update from @mreynolds: - Issue set to the milestone: 1.3.10 (was: 1.4.1)
a514aba..d73cdd1 389-ds-base-1.4.3 01b7ef7..b4d2e3a 389-ds-base-1.4.2 8409e48..d3c792b 389-ds-base-1.4.1 895f220..98826d9 389-ds-base-1.3.10
Metadata Update from @tbordaz: - Issue close_status updated to: fixed - Issue status updated to: Closed (was: Open)
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/4121
If you want to receive further updates on the issue, please navigate to the github issue and click on subscribe button.
subscribe
Thank you for understanding. We apologize for all inconvenience.
Metadata Update from @spichugi: - Issue close_status updated to: wontfix (was: fixed)
Login to comment on this ticket.