It is possible that the same csn is generated twice and so replication can fail.
[03/Apr/2018:11:43:36.488654204 +0200] conn=1 op=12 ADD dn="cn=sub3,cn=test_container,dc=example,dc=com" [03/Apr/2018:11:43:36.873066355 +0200] conn=1 op=12 RESULT err=0 tag=105 nentries=0 etime=0.0384566322 csn=5ac34cc8000100020000 [03/Apr/2018:11:43:36.875537397 +0200] conn=1 op=14 ADD dn="cn=sub4,cn=test_container,dc=example,dc=com" [03/Apr/2018:11:43:37.120083958 +0200] conn=1 op=14 RESULT err=0 tag=105 nentries=0 etime=0.1755177706 csn=5ac34cc8000100020000
in the error log, there is this:
master
[03/Apr/2018:11:43:36.686084468 +0200] - DEBUG - csngen_adjust_time - gen state before 5ac34cc80002:1522748616:0:0 [03/Apr/2018:11:43:36.697749611 +0200] - DEBUG - csngen_adjust_time - gen state after 5ac34cc80001:1522748616:0:0
It was detected when ruinning one of the conflict tests. The trigger seems to be a sequence of ADD operations which generate csns with several sequence numbers and an csn generator adjustment during this load
Metadata Update from @lkrispen: - Custom field component adjusted to None - Custom field origin adjusted to None - Custom field reviewstatus adjusted to None - Custom field type adjusted to None - Custom field version adjusted to None
<img alt="0001-Ticket-49631-same-csn-generated-twice.patch" src="/389-ds-base/issue/raw/files/9252b3bf64e6754dc18b4cba7ec2bf25054b184ee6738976a44a0b5f6d050a04-0001-Ticket-49631-same-csn-generated-twice.patch" />
Metadata Update from @mreynolds: - Custom field reviewstatus adjusted to ack (was: None)
To ssh://pagure.io/389-ds-base.git 0a5e39f..dbc4a24 master -> master
To ssh://pagure.io/389-ds-base.git 52bc5d0..e82bba7 389-ds-base-1.3.7 -> 389-ds-base-1.3.7
To ssh://pagure.io/389-ds-base.git 804002e..acd3a91 389-ds-base-1.3.8 -> 389-ds-base-1.3.8
Metadata Update from @mreynolds: - Issue set to the milestone: 1.3.7.0
This bug is a consequence of a side effect of https://pagure.io/389-ds-base/issue/49619. https://pagure.io/389-ds-base/issue/49619 being already pushed in 1.3.6, pushing this patch also in 1.3.6
To ssh://pagure.io/389-ds-base.git 31ba1e7..99ba446 389-ds-base-1.3.6 -> 389-ds-base-1.3.6
Metadata Update from @mreynolds: - Issue close_status updated to: fixed - Issue status updated to: Closed (was: Open)
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/2690
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)
Login to comment on this ticket.