Le 03/09/2012 22:45, Quanah Gibson-Mount a écrit :
--On Monday, September 03, 2012 3:52 PM +0200 Guillaume Rousse guillomovitch@gmail.com wrote:
I can't change ldap version easily, and I'd rather return to classic master-slave setup if the problem is not fixable otherwise.
I would advise you to read the CHANGES file and look at all the fixes for Syncrepl and MMR since 2.4.23 was released, and then hopefully you realize that either upgrading the *patch* level or going back to classic provider-replica setup is the wise choice.
Since the CHANGES file is publicly available on the web, I'm somewhat unclear as to why you haven't already read it over and come to a very quick and easy conclusion.
I did, of course.
However, just the number of issues isn't enough to distinguish between corner-case and immediate issues. Given than I've been running ldap server 2.4.19 in multi-master modes for years without effective problems, I'm quite used to moderate the usual 'you should never run anything else than the latest version otherwise everything will blow up' advice. Also, I'm in a very low-concurrency setup, and I could easily make sure 99% of write operations always apply on a single server.
BTW, I jsut figured than multiple CSNcontext values was perfectly normal: one is expected per data provided, and the third value (the one labelled with rid 0) was due to artifacts of my initial dataset.