This is a clone of bz 1552698
We have observed in a read only consumer that the operations are not completely serialized. This should not be a problem except when we add a parent and inmediately after, a child. If the child is processed before the parent or the parent has not finished to be processed, the child could fail to be added. Or a glue entry created, as we have seen already in a customer case. Logs:
[05/Mar/2018:22:59:36.576352590 -0800] conn=5952102 op=800 ADD dn="ou=parent,ou=Projects,dc=example,dc=com" [05/Mar/2018:22:59:36.577978254 -0800] conn=5952102 op=801 ADD dn="ou=child,ou=parent,ou=Projects,dc=example,dc=com" [05/Mar/2018:22:59:36.647458809 -0800] conn=5952102 op=801 RESULT err=0 tag=105 nentries=0 etime=0.073000 csn=5a9e3c58000003e90000 [05/Mar/2018:22:59:36.651239085 -0800] conn=5952102 op=802 ADD dn="ou=child2,ou=parent,ou=Projects,dc=example,dc=com" [05/Mar/2018:22:59:36.651830303 -0800] conn=5952102 op=800 RESULT err=0 tag=105 nentries=0 etime=0.078000 csn=5a9e3c57000003e90000
errors:
[05/Mar/2018:22:59:36.640046623 -0800] - NOTICE - NSMMReplicationPlugin - create_glue_entry - conn=5952102 op=801 csn=5a9e3c58000003e90000: Created glue entry ou=parent,ou=Projects,dc=example,dc=com uniqueid=dbc0c281-210b11e8-bb36c1a8-ea47160f reason missingEntry
Metadata Update from @lkrispen: - Custom field component adjusted to None - Custom field origin adjusted to None - Custom field reviewstatus adjusted to None - Custom field rhbz adjusted to https://bugzilla.redhat.com/show_bug.cgi?id=1552698 - Custom field type adjusted to None - Custom field version adjusted to None
<img alt="0001-Ticket-49696-replicated-operations-should-be-seriali.patch" src="/389-ds-base/issue/raw/files/b248df7196a8febe435f1ce4aa5e050fbe753734a0b9f6cdc8ca35b9169fd331-0001-Ticket-49696-replicated-operations-should-be-seriali.patch" />
Metadata Update from @lkrispen: - Custom field reviewstatus adjusted to review (was: None)
The patch looks good to me
Metadata Update from @tbordaz: - Custom field reviewstatus adjusted to ack (was: review)
committed
To ssh://pagure.io/389-ds-base.git 15ff2e3..0282ef2 master -> master
To ssh://pagure.io/389-ds-base.git de9fb25..40178b5 389-ds-base-1.3.8 -> 389-ds-base-1.3.8
To ssh://pagure.io/389-ds-base.git 9c2ec69..dc719ea 389-ds-base-1.3.7 -> 389-ds-base-1.3.7
Metadata Update from @mreynolds: - Issue close_status updated to: fixed - Issue set to the milestone: 1.3.7.0 - Issue status updated to: Closed (was: Open)
b45afc2..c154889 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/2755
If you want to receive further updates on the issue, please navigate to the github issue and click on subscribe button.
subscribe
Thank you for understanding. We apologize for all inconvenience.
Metadata Update from @spichugi: - Issue close_status updated to: wontfix (was: fixed)
Log in to comment on this ticket.