Learn more about these different git repos.
Other Git URLs
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.
Fields changed
milestone: NEEDS_TRIAGE => SSSD 1.10.0 rhbz: => todo
proposed_priority: => Important
Cleaning the 1.10 milestones before putting tickets into it.
milestone: SSSD 1.10.0 => Temp milestone
Moving planned features and bug fixes into the 1.10 bucket.
milestone: Temp milestone => SSSD 1.10.0
Moving all the features planned for 1.10 release into 1.10 beta.
milestone: Temp milestone => SSSD 1.10 beta
priority: major => minor
priority: minor => major
design: => design_review: => 0 fedora_test_page: => summary: Optimize transaction for RFC2307bis group lookups => [RFE] Optimize transaction for RFC2307bis group lookups type: defect => enhancement
selected: => Not need
Moving tickets that are not a priority for SSSD 1.10 into the next release.
milestone: SSSD 1.10 beta => SSSD 1.11 beta
mark: => 0
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
Re-setting priority of 1.13 backlog tickets used for planning.
priority: critical => major
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
rhbz: todo => 0
Metadata Update from @sgallagh: - Issue set to the milestone: SSSD 1.13 backlog
SSSD is moving from Pagure to Github. This means that new issues and pull requests will be accepted only in SSSD's github repository.
This issue has been cloned to Github and is available here: - https://github.com/SSSD/sssd/issues/2412
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.
Login to comment on this ticket.