Bug 1921861

Summary: Changelog cache can upload updates from a wrong starting point (CSN)
Product: Red Hat Enterprise Linux 7 Reporter: mreynolds
Component: 389-ds-baseAssignee: thierry bordaz <tbordaz>
Status: CLOSED WONTFIX QA Contact: RHDS QE <ds-qe-bugs>
Severity: high Docs Contact:
Priority: unspecified    
Version: 7.9CC: czinda, ds-qe-bugs, ldap-maint, lmiksik, mreynolds, msauton, sgouvern, tbordaz, tmihinto, toneata
Target Milestone: rcKeywords: Triaged
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: sync-to-jira
Fixed In Version: 389-ds-base-1.3.10.2-12.el7_9 Doc Type: If docs needed, set a value
Doc Text:
Copy of original BZ 1898541 Doc text .The replication session update speed is now enhanced Previously, when the changelog contained larger updates, the replication session started from the beginning of the changelog. This slowed the session down. The using of a small buffer to store the update from a changelog during the replication session caused this. With this update, the replication session checks that the buffer is large enough to store the update at the starting point. The replication session starts sending updates immediately.
 Story Points: ---
Clone Of: 1898541 Environment:
Last Closed: 2022-07-28 07:44:46 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1898541, 1972626    
Bug Blocks:    

Comment 6 sgouvern 2022-07-12 12:09:13 UTC 
I will in a 1st step verify it is actually fixed with 389-ds-base-1.3.10.2-13.el7_9, attached to https://errata.devel.redhat.com/advisory/81714 
Then if it is, I will double check how the Bz can be attached to the errata, even after it is SHIPPED.
Comment 7 RHEL Program Management 2022-07-28 07:44:46 UTC 
After evaluating this issue, there are no plans to address it further or fix it in an upcoming release.  Therefore, it is being closed.  If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.