New subject: [Issue 9361] accesslog logpurge generates new CSNs for its deletes

2 Oct 2020


      https://bugs.openldap.org/show_bug.cgi?id=9361
Issue ID: 9361
           Summary: accesslog logpurge generates new CSNs for its deletes
           Product: OpenLDAP
           Version: 2.4.53
          Hardware: All
                OS: All
            Status: UNCONFIRMED
          Severity: normal
          Priority: ---
         Component: overlays
          Assignee: bugs@openldap.org
          Reporter: hyc@openldap.org
  Target Milestone: ---
The delete operations that are performed by logpurge are for internal
bookkeeping purposes and should not have new CSNs attached to them. In
the current code, since each delete has a new valid CSN, the logDB's
contextCSN becomes newer than its main DB's, and this can trigger the
syncprov on the logDB to send NEW_COOKIE messages to all delta consumers.
Meanwhile, the mainDB's contextCSN hasn't changed. As a result, the
consumers' contextCSN for that SID will be newer than the provider's.
Fix coming shortly.
-- 
You are receiving this mail because:
You are on the CC list for the issue.

[Issue 9361] New: accesslog logpurge generates new CSNs for its deletes