https://bugs.openldap.org/show_bug.cgi?id=9694
Issue ID: 9694 Summary: Can Delta-sync’s changelog be based on a sessionlog? Product: OpenLDAP Version: 2.5.7 Hardware: All OS: All Status: UNCONFIRMED Keywords: needs_review Severity: normal Priority: --- Component: documentation Assignee: bugs@openldap.org Reporter: dpa-openldap@aegee.org Target Milestone: ---
In the replication terminology, the terms sessionlog and accesslog are used. sessionlog is created by the syncprov-overlay/syncprov-sessionlog directive; accesslog is created in first place by the accesslog overlay.
Delta-syncrepl introduces an additional term: changelog. The example at https://www.openldap.org/devel/admin/replication.html#Delta-syncrepl%20Provi... uses accesslog for the changelog.
The documentation is unclear, whether the changelog must be backed on accesslog-database, or it can be backed also on a sessionlog. (⇔Is delta-sync happy just with a sessionlog?)
The documentation in slapo-syncprov(5) for syncprov-nopresent says “This value should only be set TRUE for a syncprov instance on top of a log database (such as one managed by the accesslog overlay).”
Is sessionlog a log database?
https://bugs.openldap.org/show_bug.cgi?id=9694
Howard Chu hyc@openldap.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |INVALID Status|UNCONFIRMED |RESOLVED
--- Comment #1 from Howard Chu hyc@openldap.org --- (In reply to dpa-openldap@aegee.org from comment #0)
In the replication terminology, the terms sessionlog and accesslog are used. sessionlog is created by the syncprov-overlay/syncprov-sessionlog directive; accesslog is created in first place by the accesslog overlay.
Delta-syncrepl introduces an additional term: changelog. The example at https://www.openldap.org/devel/admin/replication.html#Delta- syncrepl%20Provider%20configuration uses accesslog for the changelog.
The documentation is unclear, whether the changelog must be backed on accesslog-database, or it can be backed also on a sessionlog. (⇔Is delta-sync happy just with a sessionlog?)
The documentation in slapo-syncprov(5) for syncprov-nopresent says “This value should only be set TRUE for a syncprov instance on top of a log database (such as one managed by the accesslog overlay).”
Is sessionlog a log database?
The slapo-syncprov(5) manpage is clear: sessionlog is in-memory only, it is not a database. It disappears upon server restart. Clearly it is not suitable for a changelog, which requires a persistent record of changes.
As always, software usage questions belong on the openldap-technical mailing list, not in the ITS.
https://bugs.openldap.org/show_bug.cgi?id=9694
Quanah Gibson-Mount quanah@openldap.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Keywords|needs_review | Status|RESOLVED |VERIFIED
--- Comment #2 from Quanah Gibson-Mount quanah@openldap.org --- 2.5 adds the ability for the sessionlog to additionally be backed onto an accesslog database, but it still an entirely separate thing from the deltas provided for delta-syncrepl and is used by both normal and delta-syncrepl configurations.
https://bugs.openldap.org/show_bug.cgi?id=9694
--- Comment #3 from dpa-openldap@aegee.org dpa-openldap@aegee.org --- slapd-config(5):olcSyncrepl says: The syncdata parameter must be set to either "accesslog" if the log conforms to the slapo-accesslog(5) log format, or "changelog" if the log conforms to the obsolete changelog format.
So “changelog” is obsolete format. The Guide uses the term changelog, without stating, that it is obsolete.
https://bugs.openldap.org/show_bug.cgi?id=9694
--- Comment #4 from Howard Chu hyc@openldap.org --- (In reply to dpa-openldap@aegee.org from comment #3)
slapd-config(5):olcSyncrepl says: The syncdata parameter must be set to either "accesslog" if the log conforms to the slapo-accesslog(5) log format, or "changelog" if the log conforms to the obsolete changelog format.
So “changelog” is obsolete format. The Guide uses the term changelog, without stating, that it is obsolete.
The guide uses "changelog" as a generic term - a persistent log of changes.
The syncrepl statement refers specifically to the old SunDS changelog format, which is obsolete.