#48235 Investigate removing memberof global lock
Closed: wontfix 6 years ago Opened 8 years ago by mreynolds.

With the introduction of backend transaction plugins the MemberOf Plugin global lock (memberof_lock()/memberof_unlock()) might no longer be needed.

The lock was introduced to keep the member updates synchronized, as under concurrent load it was possible for members to not have the correct memberOf value(either missing or incorrect, etc). This should no longer be an issue with the plugin now being a backend transaction plugin, but it still needs to be investigated.


Per triage, push the target milestone to 1.3.6.

Metadata Update from @nhosoi:
- Issue set to the milestone: 1.3.6.0

7 years ago

Metadata Update from @mreynolds:
- Issue close_status updated to: None
- Issue set to the milestone: 1.3.7 backlog (was: 1.3.6.0)

6 years ago

Metadata Update from @mreynolds:
- Issue set to the milestone: 1.4 backlog (was: 1.3.7 backlog)

6 years ago

Customer hitting a dead lock that would be fixed if this ticket is applied. Starting investigation...

Metadata Update from @mreynolds:
- Custom field reviewstatus adjusted to None
- Custom field rhbz adjusted to https://bugzilla.redhat.com/show_bug.cgi?id=1501058

6 years ago

Metadata Update from @mreynolds:
- Issue assigned to mreynolds

6 years ago

I agree that if this lock to prevent concurrent updates, it is no required today as memberof is a BETXN plugins.
Need to confirm the purpose of that lock.

Metadata Update from @mreynolds:
- Custom field reviewstatus adjusted to review (was: None)
- Issue set to the milestone: 1.3.6.0 (was: 1.4 backlog)

6 years ago

The fix looks very good to me. ACK.
I think you can get rid of 'plhash.h' in memberof.c now.

Metadata Update from @tbordaz:
- Custom field reviewstatus adjusted to ack (was: review)

6 years ago

I agree, this looks really good. Thanks Mark!

@tbordaz - we still need that header in memberof.c

FYI, I also ran all the CI tests that use memberof and they all passed.

b761460..184b8a1 389-ds-base-1.3.6 -> 389-ds-base-1.3.6

0658297..8915d8d 389-ds-base-1.3.7 -> 389-ds-base-1.3.7

2b8b6db..df4492b master -> master

Metadata Update from @mreynolds:
- Issue close_status updated to: fixed
- Issue status updated to: Closed (was: Open)

6 years ago

Fix cherry-pick errors

34a184a..3eb443b master -> master

8915d8d..4471b73 389-ds-base-1.3.7 -> 389-ds-base-1.3.7

e6ac5ec..80c8795 389-ds-base-1.3.6 -> 389-ds-base-1.3.6

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

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)

3 years ago

Login to comment on this ticket.

Metadata