389-ds-base

#47963 RFE - memberOf - add option to skip nested group lookups during delete operations
Closed: wontfix Opened by mreynolds.

Closed: wontfix
Reopen Issue

The recursive nested group lookups performed during a group delete operation can take a very long time to complete if there are very large static groups(groups with with over 10K members). If there are no nested groups, then it would be nice to have an option to skip the nested group check, which would significantly improve delete performance.

I think you need to free this skip_nested:
{{{
if ((skip_nested = slapi_entry_attr_get_charptr(e, MEMBEROF_SKIP_NESTED_ATTR))){
}}}
and this one
{{{
skip_nested = slapi_entry_attr_get_charptr(e, MEMBEROF_SKIP_NESTED_ATTR);
}}}

Replying to [comment:2 rmeggins]:

I think you need to free this skip_nested:
{{{
if ((skip_nested = slapi_entry_attr_get_charptr(e, MEMBEROF_SKIP_NESTED_ATTR))){
}}}
and this one
{{{
skip_nested = slapi_entry_attr_get_charptr(e, MEMBEROF_SKIP_NESTED_ATTR);
}}}

Yeah, nice catch. New patch attached.

c973e71..b01cf4d master -> master
commit b01cf4dbf9c8995081da81e39f8766d2df9e0c2d
Author: Mark Reynolds mreynolds@redhat.com
Date: Mon Nov 24 16:58:57 2014 -0500

44f84b3..ecd34a5 389-ds-base-1.3.3 -> 389-ds-base-1.3.3
commit ecd34a544fd0d34cab863b7e15983ca1e243ebe7

9c44c63..9cce9c4 389-ds-base-1.3.2 -> 389-ds-base-1.3.2
commit 9cce9c4bc7b212a7c819ee2c3ea040ed5b282017

cd06271..250fcdb 389-ds-base-1.3.1 -> 389-ds-base-1.3.1
commit 250fcdbb463d2f4597a61ef1e364f71fa01ef1be

0c47dfb..ec0b121 389-ds-base-1.2.11 -> 389-ds-base-1.2.11
commit ec0b121e65800e4664fafb9001b0e9118ca45464

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

c5cc125..d8e8119 master -> master
commit d8e8119e92c6d872e317bbae5d59a08d80cb0966
Author: Mark Reynolds mreynolds@redhat.com
Date: Wed Nov 26 16:57:05 2014 -0500

ecd34a5..ae06f96 389-ds-base-1.3.3 -> 389-ds-base-1.3.3
commit ae06f9626255abe9687c110bcd85fc8287d3ec99

9cce9c4..919f30c 389-ds-base-1.3.2 -> 389-ds-base-1.3.2
commit 919f30ca67e278584cfdbdf0c6c86ba38429b21b

250fcdb..664b4f1 389-ds-base-1.3.1 -> 389-ds-base-1.3.1
commit 664b4f126b356854806762f880274b5531c83fb1

ec0b121..116dcbd 389-ds-base-1.2.11 -> 389-ds-base-1.2.11
commit 116dcbd8094491b0249ed0bae4c00f08b478c3ab

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

I have done some tests and I have found some problems with this config option. The plugin seems not to be working.

Re opening this bug.

Will give further details in the BZ with my testcase.

4681fab..248b471 master -> master
commit 248b471c86dbd7ed6a86e9def90a0d7a9858ed91
Author: Mark Reynolds mreynolds@redhat.com
Date: Tue Feb 3 12:52:40 2015 -0500

d65945e..2f24d28 389-ds-base-1.3.3 -> 389-ds-base-1.3.3
commit 2f24d28cf608e5ecd580be82fea8c51e28429329

a204469..70d5fe6 389-ds-base-1.3.2 -> 389-ds-base-1.3.2
commit 70d5fe69846482bb82723e300389469924c2cd85

bf55d5a..ddcab8a 389-ds-base-1.3.1 -> 389-ds-base-1.3.1
commit ddcab8af51c8b0a787dc630bce3a0b34c446c973

d26ed48..ffc784c 389-ds-base-1.2.11 -> 389-ds-base-1.2.11
commit ffc784c20554edcfa496472a3b438e31d20d6a4a

Metadata Update from @mreynolds:
- Issue assigned to mreynolds
- Issue set to the milestone: 1.2.11.33

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

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
None
None
None
Normal
ack
RHCust
Static archive. pagure.io was sunset in 2026; this is a read-only snapshot.
Red Hat Logo

Fedora is sponsored by Red Hat. Learn more about the relationship between Red Hat and Fedora »

© Red Hat, Inc. and others.