You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There is a sysdb transaction that is started in {{{sdap_get_groups_process()}}} and terminated in {{{sdap_get_groups_done()}}}. However, during this processing, it is possible for RFC2307bis lookups to go back to the LDAP server. The result is that the sysdb is holding onto a transaction for far too long, which can block other operations.
We need to rework this code so that we gather all necessary data first and then only start (and finish) a transaction in a single function.
Unless there are external groups or idviews used, we only use a single transaction already. Therefore I think this issue would better be solved with #2943 which provides a much better description, so I'm closing this ticket in favor of #2943.
resolution: => duplicate
sensitive: => 0
status: new => closed
Cloned from Pagure issue: https://pagure.io/SSSD/sssd/issue/1370
There is a sysdb transaction that is started in {{{sdap_get_groups_process()}}} and terminated in {{{sdap_get_groups_done()}}}. However, during this processing, it is possible for RFC2307bis lookups to go back to the LDAP server. The result is that the sysdb is holding onto a transaction for far too long, which can block other operations.
We need to rework this code so that we gather all necessary data first and then only start (and finish) a transaction in a single function.
Comments
Comment from dpal at 2012-06-14 15:25:38
Fields changed
milestone: NEEDS_TRIAGE => SSSD 1.10.0
rhbz: => todo
Comment from dpal at 2012-08-14 01:59:15
Fields changed
proposed_priority: => Important
Comment from dpal at 2012-09-04 23:13:30
Cleaning the 1.10 milestones before putting tickets into it.
milestone: SSSD 1.10.0 => Temp milestone
Comment from dpal at 2012-09-04 23:15:24
Moving planned features and bug fixes into the 1.10 bucket.
milestone: Temp milestone => SSSD 1.10.0
Comment from dpal at 2012-09-04 23:18:32
Fields changed
milestone: SSSD 1.10.0 => Temp milestone
Comment from dpal at 2012-09-04 23:20:25
Moving all the features planned for 1.10 release into 1.10 beta.
milestone: Temp milestone => SSSD 1.10 beta
Comment from dpal at 2012-09-04 23:50:13
Fields changed
priority: major => minor
Comment from dpal at 2012-09-04 23:52:19
Fields changed
priority: minor => major
Comment from dpal at 2012-10-25 14:53:38
Fields changed
design: =>
design_review: => 0
fedora_test_page: =>
summary: Optimize transaction for RFC2307bis group lookups => [RFE] Optimize transaction for RFC2307bis group lookups
type: defect => enhancement
Comment from dpal at 2012-12-20 23:33:42
Fields changed
selected: => Not need
Comment from dpal at 2013-01-02 15:32:08
Moving tickets that are not a priority for SSSD 1.10 into the next release.
milestone: SSSD 1.10 beta => SSSD 1.11 beta
Comment from dpal at 2014-09-26 18:49:56
Fields changed
mark: => 0
Comment from jhrozek at 2015-02-10 15:01:23
We might need to take another look at transactions to optimize the server mode.
changelog: =>
milestone: SSSD 1.13 beta => SSSD 1.13 backlog
priority: major => critical
review: => 0
Comment from jhrozek at 2015-02-12 20:55:41
Re-setting priority of 1.13 backlog tickets used for planning.
priority: critical => major
Comment from jhrozek at 2016-02-16 16:04:02
Unless there are external groups or idviews used, we only use a single transaction already. Therefore I think this issue would better be solved with #2943 which provides a much better description, so I'm closing this ticket in favor of #2943.
resolution: => duplicate
sensitive: => 0
status: new => closed
Comment from jhrozek at 2016-09-10 11:28:22
Fields changed
rhbz: todo => 0
Comment from sgallagh at 2017-02-24 14:24:16
Metadata Update from @sgallagh:
The text was updated successfully, but these errors were encountered: