https://bugs.openldap.org/show_bug.cgi?id=9753
--- Comment #7 from Howard Chu hyc@openldap.org --- (In reply to Michael Ströder from comment #6)
What is the impact of this issue?
Given that admin guide advices to index entryCSN and entryCSN is updated with a MOD_REPLACE (according to reqMod values in accesslog DB) this issue could cause various replication issues hard to track down.
This is precisely the impact we observed.
Also the fix has not been back-ported to RE24 branch yet. Are there any plans to add the fix also to release 2.4.60?
Not at the moment. 2.4 EOL was announced at the beginning of this year. Officially 2.4 is dead. There's some debate about whether to resurrect it for this. I will state up front: non-contributors get no vote.