Issue 6942 - updateref config is inadequate
Summary: updateref config is inadequate
Status: UNCONFIRMED
Alias: None
Product: OpenLDAP
Classification: Unclassified
Component: slapd (show other issues)
Version: unspecified
Hardware: All All
: High enhancement
Target Milestone: 2.7.0
Assignee: OpenLDAP project
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-05-12 04:32 UTC by Howard Chu
Modified: 2023-11-16 16:58 UTC (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this issue.
Description Howard Chu 2011-05-12 04:32:24 UTC 
Full_Name: Howard Chu
Version: 2.4.x
OS: 
URL: ftp://ftp.openldap.org/incoming/
Submission from: (NULL) (76.94.188.8)
Submitted by: hyc


This was pointed out on the mailing list, I've lost the exact message now.

We allow multiple consumers in a single DB, but we only allow a single updateref
on the DB. This is clearly broken; we need to be able to specify an updateref
per consumer.

This also ties in with other discussions about moving updateref processing out
of the frontend. Doing it in the frontend was OK back in OpenLDAP 2.3 and
earlier, but not any more.
Comment 1 OpenLDAP project 2017-04-12 20:30:37 UTC 
See also ITS#6531
Comment 2 Quanah Gibson-Mount 2017-04-12 20:30:37 UTC 
changed notes
moved from Incoming to Software Enhancements
Comment 3 Quanah Gibson-Mount 2022-06-13 07:23:09 UTC 
Fairly critical for 2.7.0 so that we can better handle replicated environments with chaining where MMR is in play.
Comment 4 Ondřej Kuzník 2023-11-16 16:58:24 UTC 
Maybe putting updateref on the syncrepl consumer configuration is a way to deal with this.