On Thu, Aug 22, 2019 at 06:32:53 -0700, Quanah Gibson-Mount wrote:
Turns out that writes failed by an overlay (slapo-unique in our case) are only logged to the accesslog, if this overlay is defined in the config BEFORE the accesslog overlay (as overlays are loaded on a stack, see topic 12.18 in the admin guide). So we now put the accesslog overlay as last instead of first.
Hm, which is against best practices because it can cause other issues, IIRC (which is why it's advised to have syncprov followed by accesslog, as the first 2 overlays in the stack). This is something that needs redoing for 2.5.
What sort of issues Quanah? Do you advise to rollback?
We currently have the following order: syncprov, unique, accesslog.
Before it was: syncprov, accesslog unique.
Are these best practices you mention documented somewhere?
Geert