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 1321126 - Replication changelog can incorrectly skip over updates
Summary: Replication changelog can incorrectly skip over updates
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: 389-ds-base
Version: 6.0
Hardware: All
OS: Linux
urgent
urgent
Target Milestone: rc
: ---
Assignee: Noriko Hosoi
QA Contact: Viktor Ashirov
URL:
Whiteboard:
Depends On:
Blocks: 1354331
TreeView+ depends on / blocked
 
Reported: 2016-03-24 17:49 UTC by Noriko Hosoi
Modified: 2020-09-13 21:49 UTC (History)
9 users (show)

Fixed In Version: 389-ds-base-1.2.11.15-82.el6
Doc Type: Bug Fix
Doc Text:
Previously, a bug in the changelog iterator buffer could in some scenarios point to an incorrect position when reloading the buffer. This could cause replication to skip parts of the changelog, and consequently some changes were not being replicated. This bug has been fixed, and replication data loss due to an incorrectly reloaded changelog buffer no longer occurs.
Clone Of:
: 1354331 (view as bug list)
Environment:
Last Closed: 2017-03-21 10:20:50 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github 389ds 389-ds-base issues 1826 0 None closed Replication changelog can incorrectly skip over updates 2020-12-09 11:05:25 UTC
Github 389ds 389-ds-base issues 2013 0 None closed replication fails because anchorcsn cannot be found 2020-12-09 11:05:27 UTC
Red Hat Product Errata RHBA-2017:0667 0 normal SHIPPED_LIVE 389-ds-base bug fix update 2017-03-21 12:35:05 UTC

Description Noriko Hosoi 2016-03-24 17:49:13 UTC 
This bug is created as a clone of upstream ticket:
https://fedorahosted.org/389/ticket/48766

In a MMR environment where all the masters are under heavy load the replication changelog cache/buffer mechanism does not always use the correct anchor csn and some updates are not sent to the consumer.  

Typically it's the very first "bulk load" read from the changelog at the start of a replication session that has issues, but it can also happen during subsequent bulk loads during the same session.
Comment 1 Noriko Hosoi 2016-03-31 17:01:57 UTC 
Justification: This bug is severe because it could cause data loss on some random replication consumer servers without being noticed.
Comment 4 Noriko Hosoi 2016-07-08 01:23:23 UTC 
Justification:

https://bugzilla.redhat.com/show_bug.cgi?id=1321124#c19
(In reply to German Parente from comment #18)
> hi Marcel,
> 
> you are right that this bug has been identified only once in case 01632462.
> But I think the reason of having this in 7.2.Z is that there's a case where
> we could have inconsistency in the different nodes under replication and
> without noticing. That's the reason why engineering wanted this bug fixed in
> rhel7.2.z

This is a very severe bug that impacts all customers who use replication.  The main issue, already mentioned by German, is that updates are silently skipped.  This leads to data inconsistency, which basically means replication is broken.  This is a worst case scenario for customers using replication, because replication is not working correctly but there are warnings/errors.  So the customer has no idea things are broken, and when storing/replicating things like credit card/bank information, passwords, or other sensitive data, this inconsistency is unacceptable.
Comment 12 errata-xmlrpc 2017-03-21 10:20:50 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, 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://rhn.redhat.com/errata/RHBA-2017-0667.html
Note You need to log in before you can comment on or make changes to this bug.