RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 2112361 - Supplier should do periodic update to avoid slow replication when a new direct update happen
Summary: Supplier should do periodic update to avoid slow replication when a new direc...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: 389-ds-base
Version: 9.0
Hardware: Unspecified
OS: Unspecified
high
unspecified
Target Milestone: rc
: 9.2
Assignee: mreynolds
QA Contact: LDAP QA Team
URL:
Whiteboard: sync-to-jira
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-07-29 13:34 UTC by thierry bordaz
Modified: 2023-05-09 08:50 UTC (History)
5 users (show)

Fixed In Version: 389-ds-base-2.2.4-3.el9
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-05-09 07:41:32 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker IDMDS-2414 0 None None None 2022-08-02 19:37:03 UTC
Red Hat Issue Tracker IDMDS-2714 0 None None None 2023-01-10 13:56:53 UTC
Red Hat Issue Tracker RHELPLAN-129676 0 None None None 2022-07-29 13:54:31 UTC
Red Hat Product Errata RHBA-2023:2274 0 None None None 2023-05-09 07:41:46 UTC

Description thierry bordaz 2022-07-29 13:34:12 UTC 
Description of problem:
In a replicated topology, if a supplier has not received any direct update for a long time (for example 3 months). When this supplier receive a direct update, its RUVelement will be selected for each replication session (lowest csn) and the session will start by scanning 3 months of updates before finding something to send.

The consequences are 
- the replication session will last a long time preventing others suppliers to send their own updates
- the replication session will be inefficient, sending few updates in a long delay
- Showing an false alarming replication lag with RUV comparison tools (a 3 months lag where actually this is a single update missing).
- risk of apparent replication breakage if the consumer closes the inactive replication connection (idletimeout or nsidletimeout)

Version-Release number of selected component (if applicable):
All version


How reproducible:


Steps to Reproduce:
1. 4 suppliers
2. configure idletimeout=15s
2. one update on all suppliers
3. multiple updates (200K) on 3 out 4 suppliers. One supplier without any update.
3. check all suppliers are in sync
4. update the last supplier.
5. wait 1min
6. do a single update on the 3 others


Actual results:
Likely the updates (6) are not replicated or with a long delay


Expected results:
replication should get in sync in few seconds.

Additional info:
Comment 1 thierry bordaz 2022-07-29 13:44:18 UTC 
An option is that each replica registers a slapi_eq_repeat task, that will do a dummy update on keep alive entry.
It should use a non indexed attribute (description ?). something like

dn: cn=keep alive 1, cn=<suffix>
objetclass:..
description: touch at 2022-07-29 13:34:19
Comment 2 mreynolds 2022-08-02 19:36:48 UTC 
Upstream ticket:

https://github.com/389ds/389-ds-base/issues/3903
Comment 3 thierry bordaz 2022-08-03 13:16:20 UTC 
Note that the upstream ticket is replication agreement focus. I think it could rather be replica oriented, like tombstone trimming thread (eq_cb_reap_tombstones).
Comment 10 bsmejkal 2023-01-19 09:33:03 UTC 
As per comment #c8 marking as VERIFIED.
Comment 12 errata-xmlrpc 2023-05-09 07:41:32 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (389-ds-base bug fix and enhancement update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2023:2274
Note You need to log in before you can comment on or make changes to this bug.